How GUI Test Studio works

The idea

You test your application by hand already: you click through a scenario and look at the screen.GUI Test Studio turns that walk-through into an automated test.You show it once, it checks it on every run.

There is no script to write.A test is made of the steps you performed and the checks that say what correct looks like, laid out on a timeline like a video edit.

There are two ways to create a test.Record it yourself: GUI Test Studio generates the test from the recording, visually, ready to run and to edit at any time.Or describe the workflow in a prompt: your AI assistant records, verifies and runs it for you through GUI Test Studio's connector, Claude, ChatGPT or a local AI model we provide or you bring, and the result is the same test.

Two apps and a runner

One installer gives you three tools that work on the same test files.

Enlarge

Enlarge

The four steps

Refining is optional: a recording is a complete test the moment you save it, with its checks already in place.You come back to GUI Test Studio when you want to change something.

What a check is

A check (assert) is a moment where the test makes sure something is right: a button is there, a text says the right thing, a dialog has closed, a list has three rows.There are visual checks, text checks and layout checks.

The GTS Engine + AI finds each element two ways.It first asks the application itself: a desktop app's accessibility information, the same information a screen reader uses, or a web page's own elements.When the application does not say, as with a game, a canvas, a remote desktop or a program drawn by its own toolkit, the engine finds the element by sight, on the screen, the way a person does.

Two ways to the same element are what make a test robust.It keeps finding a button after the code behind it changed, the window moved or the layout shifted, and it works whatever your app is: a website, a desktop program, a game or a phone shown on your screen, built with any technology.

Finding the element is the first half of a check.The second half always compares what is on the screen with what you expect, so a test catches what your users would see.

Enlarge

What you can use it for

See Test a feature before it exists for the last one.

During development, not only at the end

Tests are not something you add once the product is finished.Create them while a feature is being built, and change them as it changes: record a new Scenario, move a step, replace what a check expects, on the timeline or by prompt.GUI Test Studio is made for that everyday editing, and every change can be undone.

Where to go next