Question 1

What is GUI Test Studio, in one sentence?

Accepted Answer

It turns what a tester does on screen into an automated end-to-end test: you record the scenario once or describe it in a prompt, polish it on a timeline like a video edit or by prompt, and replay it on every build, with a report that shows exactly what changed.

Question 2

Do I need to know how to code?

Accepted Answer

No. Creating a test is simply a walkthrough of your app, done by hand the first time only, or a prompt that describes it. From then on you can run it and edit it anytime, visually or by prompt. Developers can still automate everything from the command line when they want to.

Question 3

Do I have to record every test by hand?

Accepted Answer

No. Describe the workflow in a prompt and your AI assistant, Claude, ChatGPT or a local AI model we provide or you bring, records, verifies and runs the test on your computer. Or record it yourself: GUI Test Studio generates the test from the recording, visually, ready to run and to edit at any time.

Question 4

What kinds of applications can I test?

Accepted Answer

Anything that shows up on a Windows screen, virtual machines included: desktop applications, web applications in any browser, applications running in a virtual machine, Android apps shown on your screen from a phone plugged in over USB, and video games, including gamepad input. The GTS Engine + AI finds each element through the application's accessibility information when it has some, and by sight on the screen when it has none, so it does not care which framework or engine the app was built with.

Question 5

How does GUI Test Studio find the elements on the screen?

Accepted Answer

With the GTS Engine + AI. It first asks the application where an element is, through its accessibility information, the same information a screen reader uses, or through the web page itself. 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 on applications other tools cannot see into. Then the engine compares what it found with what you expect.

Question 6

What is the GTS Engine + AI?

Accepted Answer

The engine behind every GUI Test Studio test. The GTS Engine finds each element, through the application's accessibility information or by sight, and checks it against what you expect, on your own computer. Its AI side, AI Smart Verification, is optional: it takes a second look at a failed check and says in plain words what changed, with a cloud model and your own key, or a local AI model we provide or you bring. On-premise or in the cloud, your choice.

Question 7

Can I create a test from a prompt without a cloud AI?

Accepted Answer

Yes. In GUI Test Runner-Recorder, Create Test From Prompt has a This computer card: a local AI model, one we provide and download once into GUI Test Studio's built-in engine, or one you bring through LM Studio or any OpenAI-compatible local server, creates the test with the same tools Claude and ChatGPT use. Your request and your screen never leave the computer, and there is no cost per test. A local AI model is slower, and best with short workflows; Claude or ChatGPT with Codex create long tests faster.

Question 8

Do I need a finished app with a user interface before I can create tests?

Accepted Answer

No. Design the screens in Figma, or in any design tool, and create the test from the design before the feature is built. That is test-driven development for the user interface: the test is ready the day the feature is, and its first run tells you, element by element, whether what was built matches what was designed.

Question 9

Does GUI Test Studio work with Figma?

Accepted Answer

Yes. A small plugin inside Figma saves your design as one file, and GUI Test Studio turns every screen into a reference picture with ready-made checks. When the design changes, a sync updates the test. There is no account to connect, and nothing is sent anywhere.

Question 10

Which operating systems does it run on?

Accepted Answer

GUI Test Studio and its runner work on Windows 10 and Windows 11 (64-bit). The application you test can be anything that is visible on that screen, including a web app or a mirrored Android phone.

Question 11

Does GUI Test Studio support Mac?

Accepted Answer

GUI Test Studio itself runs on Windows. Run macOS in a virtual machine on a Windows computer, and your Mac application is tested on screen like any other.

Question 12

What exactly can a test check?

Accepted Answer

That a visual element is there (or gone, or shown a given number of times), that a text is on screen, that a changing value such as a date or a total has the right format, that the layout of a screen is still arranged the same way, and several of these at once as a group. Every check can hold different expected versions for different environments.

Question 13

A test includes a video recording. How large is a test file?

Accepted Answer

As light as you need it to be. A test (.GTS) keeps its visual reference, the recording, pictures or Figma designs, because that is what you edit it with. To run it, export it as a runner test (.GTR): a lightweight version without the recording, made only for running. That is the file to give a build machine or a colleague who only runs tests.

Question 14

How is this different from screenshot comparison tools?

Accepted Answer

Those tools compare whole pages and drown you in differences you do not care about. GUI Test Studio checks the elements you chose, in the area you chose. The Confidence Report shows the expected and the actual result of every check side by side, compares them, and gives its verdict in plain, human-readable language. It also fills in a bug report for you, ready for the QA engineer to hand to a developer or an AI agent.

Question 15

Is GUI Test Studio an RPA tool?

Accepted Answer

No. It works on the screen the way RPA tools do, clicking and typing like a person, but it is built for testing: it checks that your application looks and behaves as expected, and reports what changed.

Question 16

Where are my tests and recordings stored?

Accepted Answer

On your own machines, in ordinary files you can keep under version control. Recordings, screenshots, test results and reports are never uploaded to us.

Question 17

Does anything ever leave my computer?

Accepted Answer

Only if you choose a cloud AI provider. AI Smart Verification is optional and off by default. If you leave it off, or use it with a local AI model, one we provide or one you bring, your data stays on your own machine. If you enable a cloud provider such as OpenAI or Anthropic's Claude, the two small pictures of a failed check are sent to that provider with your own API key, to explain what changed. Nothing is ever sent to us.

Question 18

Does the GTS Engine + AI run in the cloud or on my computer?

Accepted Answer

The engine itself, finding the elements and checking them, always runs on your own computer. For its AI side you choose: your data, your privacy. AI Smart Verification can run on a local AI model, one we provide or one you bring, or through an AI provider such as OpenAI or Anthropic's Claude with your own key. If a local model is not an option for you, contact us: we can serve a cloud model for you, as an optional service priced separately from your subscription.

Question 19

With a cloud AI provider, how many tokens does GUI Test Studio use?

Accepted Answer

Very few. The GTS Engine + AI does most of the work on your computer: every check is first decided there, and its AI side is asked only about the checks that failed, with small pictures of the element instead of the whole screen. A test that passes costs nothing, and each answer is kept with its run, so reopening a report asks nothing again. The exact amount depends on your tests and on the model you choose, and you can always switch to a local model, one we provide or one you bring, which costs nothing per check.

Question 20

How does the free trial work?

Accepted Answer

Create an account with your email address, or with Google, and you get 15 days with every feature. We do not ask for any payment details, so nothing is charged and nothing renews by itself. When the trial ends you choose a plan, or simply stop.

Question 21

How are users and seats counted?

Accepted Answer

Pricing is per user, and each user is one seat: one person on one computer. Individual is one seat. Small Team covers 2 to 5 users and Enterprise starts at 6 users, with a price we agree together: contact us. Each user signs in to the apps on their own computer with their own account.

Question 22

How do I share my plan with my team?

Accepted Answer

From your account page. As the owner of the plan you invite each person by email; they join with an account of their own and use the apps on their computer. You can remove a member at any time, and a build agent gets a key of its own. When the plan ends, it ends for everyone.

Question 23

Can I move GUI Test Studio to another computer?

Accepted Answer

Yes. Deactivate the old computer on your account page and sign in on the new one: your account and your plan follow you. A seat moves to another computer at most once every 30 days.

Question 24

Can I cancel or change my plan?

Accepted Answer

Yes, at any time from your account. A cancelled subscription keeps working until the end of the period you paid for. Changing the number of users is done from the same place.

Question 25

Who handles taxes and invoices?

Accepted Answer

Payments are processed by Lemon Squeezy, our merchant of record. They calculate the right VAT or sales tax for your country and send a proper invoice for every payment.

Question 26

Can we ask for new features or custom work?

Accepted Answer

Yes, as long as you are on the Enterprise plan. Feature requests and features built for your needs are part of it. Professional Services, where our team creates your tests for you, are a separate service with its own price, not included in the subscription. Tell us what your team needs and we agree the details together.

Question 27

Does it work with our CI/CD pipeline?

Accepted Answer

Yes. The runner has a command-line version that runs a test without a window, returns an exit code, and writes JUnit, JSON and Markdown results plus every picture of a failure. Ready-made examples cover GitHub Actions, GitLab CI/CD, Azure DevOps, Jenkins and TeamCity.

Question 28

What happens when the design changes on purpose?

Accepted Answer

Open the run's Confidence Report, look at the new picture, and accept it as the new expected result. One click per check, or all failed checks at once, and every accept can be undone before you save.

Question 29

What languages does the app speak?

Accepted Answer

The applications are available in English, French, Spanish, German and Italian, and text checks can read English, French, Spanish, German, Italian, Portuguese, Dutch and Arabic.

Question 30

Is support included?

Accepted Answer

Yes, on every plan, by email. We read every message ourselves, and many of the features in GUI Test Studio today started as a customer's question.

Questions, answered plainly

The product

Your data and security

Trial, pricing and billing

Teams and pipelines