GUI test automation for Windows

Click once.
Test forever.

GUI Test Studio records real mouse and keyboard input in your Windows application and replays it automatically — ideal for checking within minutes, after every update, whether everything still works as expected.

⬇ Download GuiTestStudio.zip

Not a rigid screen replay: GUI Test Studio re-finds click targets via image anchors even after layout shifts, compares screen states with adjustable tolerance instead of strict pixel matching — and, if you like, lets an AI judge whether the on-screen content is actually correct, not just pixel-identical.

Step 1
*Click* on "Save"

You use it
exactly as usual.

Step 2

Every click and every input automatically becomes a named test step — including an image anchor and the window/control name.

🖱
🖼
🧭

Broken down into
test steps automatically.

Found!
The key idea
Recording
Replay after update

Same click.
New position, still found.

Even if the layout shifts slightly after an update, GUI Test Studio reliably re-finds the click target via its image anchor — instead of rigidly sticking to fixed coordinates.

Step 3
✅ Passed

If a step fails:
retried automatically.

Result
M R AI

Done. Traceable.
Ready right away.

New

An optional chart shows CPU, RAM and sub-process count of the monitored target process as a time series — the last 2 minutes at a 1-second interval, each series toggled individually via the legend, height freely adjustable via a splitter.

Live
CPU % RAM Sub-processes

Nothing missed: the trend stays visible even after a brief CPU spike — not just the current value in the status bar.

Resource trend
at a glance.

Core features

What GUI Test Studio does for you

From recording to the finished report, GUI Test Studio covers the entire GUI-testing workflow — with no scripting required.

🖱
Recording

A global mouse/keyboard capture automatically detects clicks, double-clicks, drags, scrolling, key presses and typed text, turning them into named test steps — including an image anchor around the click point plus the window and control name, so it stays clear what happened even without the recording open.

Per-step image anchor Window/control detection F8/F9/ESC hotkeys
Replay

Recorded test cases run again automatically — with configurable retries on failure, tolerant image comparison, and "wait for image state" for elements that only appear after a delay. Any test case can also resume from an arbitrary step with one click.

Retry logic Tolerance control Stop on error
🤖
AI verification

Instead of only comparing pixels, Claude judges a screenshot against a freely worded instruction — e.g. "The dialog shows no error message and all required fields are filled in" — and returns a verdict with reasoning. On request, the AI also explains why a failed image checkpoint failed.

Content-based checks Automatic failure analysis
📊
Metrics

During every test run, CPU usage, RAM, thread/handle/module counts and the number of sub-processes are continuously captured — live in the status bar and an optional overlay that follows the cursor, and stored in structured form in the run result.

Live overlay x86/x64 RAM thresholds
🐞
Diagnostics

.NET exceptions are captured with a real, symbolicated stack trace (via ClrMD), the target application's log/crash directory is continuously scanned for error patterns, and window/navigation and focus changes are logged automatically.

ClrMD stack traces Log monitoring
📄
Reports

Every run automatically produces an HTML report with screenshots, diff images for failed image comparisons, and any AI reasoning — one click from the app opens it in the browser.

HTML report Diff images
How it works

From click to test report
in four steps

No script, no coding required. GUI Test Studio records what you do and repeats it reliably — even after layout shifts in the next update.

Create a project

Pick the target application and set the starting position for recording & playback (monitor, fullscreen or a fixed resolution).

Record

Use the application as usual — clicks, input and image checkpoints automatically become named test steps.

Replay

Run the test case automatically — with retries on failure and robust targeting via image anchors.

Review

The live log, metrics, diagnostic entries and HTML report show exactly what happened — and where it didn't.

Capabilities

More than a simple recorder

GUI Test Studio is built for robust, repeatable test runs — with warning thresholds, diagnostic depth and project management that go beyond plain replay.

Resource monitoring
RAM warning thresholds for x86 and x64

Each project can hold separate RAM thresholds for 32-bit and 64-bit target processes. The bitness of the monitored process is detected automatically — once current RAM usage exceeds the matching threshold, the live display turns red instantly.

Target process (x64) — 412 MB
Below threshold
Target process (x86) — 1,180 MB
Threshold exceeded
AI verification
Verify meaning, not just pixels

A freely worded instruction is enough — Claude judges the screenshot and returns a verdict with reasoning, right there as a test step in the log.

"The dialog shows no error message and all required fields are filled in."
✅ Passed — no error message visible, all fields filled in.
Diagnostics
.NET exceptions with real stack traces

ClrMD captures .NET exceptions from the target application with a symbolicated stack trace — complemented by log/crash directory monitoring with custom search terms, and automatically detected window, navigation and focus changes. An optional, experimental debugger attach additionally catches native exceptions.

NullReferenceException in OrderService.Save
Stack trace captured
"Edit Order" window opened
Navigation detected
Image anchor search
Robust against layout shifts

Click targets are re-found via an image patch around the recorded point rather than fixed coordinates alone — patch size and minimum match score can be fine-tuned in settings.

x86 & x64
Matched to your target app

GUI Test Studio ships as a standalone x86 and x64 build — important for accurate ClrMD diagnostics, since a bitness mismatch between the test tool and the target process prevents reading memory information at all.

Live log
At a glance: active, passed, failed

While a test case runs, the step currently executing highlights in pastel blue in the test-step list; completed steps stay marked green or red depending on the outcome — all semi-transparent, so thumbnails and description text stay readable underneath.

Usability
Test run log, freely resizable

A GridSplitter between the main area and the test-run log can be dragged to resize — handy when you need to keep an eye on many log or diagnostic lines at once.

Project management
Project properties with central default values

Project properties let you set the name, log/crash directory, monitor and target size, and the RAM warning thresholds for x86 and x64 per project. Default values defined in the general settings are applied automatically when a new project is created — every project stays independently editable afterwards.

Rename project Log directory Monitor & resolution RAM thresholds Central defaults
Read more

Documentation

Three short guides — depending on whether you're setting up GUI Test Studio, using it for the first time, or want to get more out of daily use.

Get started

Ready to automate your test flows?

Reach out — we're happy to show you how GUI Test Studio fits into your environment.

⬇ Download GuiTestStudio.zip

Or get in touch directly →