Small settings with a big impact — from image-anchor accuracy to a fully adjustable workspace.
All three hotkeys work at any time while recording, regardless of which window currently has focus.
During playback, the search first checks near the originally recorded position before searching the whole window — this speeds up the search and reduces false matches on recurring UI elements. Two knobs in the general settings:
Tip: If a step starts failing more often after an update, check the match score shown in the report first — often a slightly lower minimum match score fixes it, no need to re-record the step.
By default, a test run stops at the first failed step. For a complete overview of every problem in a test case, disable "Stop on error" in the header — the test case then runs all the way through, and the report shows every failed step at once instead of just the first one.
The optional metrics overlay ("Metrics overlay" checkbox) shows CPU, RAM, threads, handles, modules and live .NET exceptions right next to the cursor — click-through by default, so it doesn't intercept recorded or replayed clicks.
The height between the main area and the test-run log can be dragged freely via a GridSplitter — handy when many log lines need to stay visible at once during a run. The columns between test steps/properties and the diagnostics panel can likewise be widened or narrowed via splitters.
The RAM warning thresholds in project properties are deliberately separate for x86 and x64 target processes, since 32-bit applications naturally hit trouble far earlier than 64-bit ones due to their limited address space. A good starting point: observe the target application's normal idle RAM usage and set the threshold just above it with a reasonable buffer — 0 disables the warning entirely if no sensible limit is known yet.