Guides
Welcome to GUI Test Studio
Streamlined visual automation for modern engineering teams.
Guided workflows that turn manual QA walkthroughs into deterministic, release-ready test suites.
/
Ctrl+K searches the whole website from any page.
New here?Start with these three
- 1How GUI Test Studio worksThe whole idea in two minutes: record a test or describe it in a prompt, refine, run, read the report.Read
- 2Your first test, step by stepRecord a short scenario, save it, run it and read its report, in about ten minutes.Read
- 3Choose the right checkNine checks, one question: what do you want to be sure of?Read
Getting started
- How GUI Test Studio worksThe whole idea in two minutes: record a test or describe it in a prompt, refine, run, read the report.
- Install and set upWhat you need, where the download is, and the few questions the apps ask the first time.
- Your first test, step by stepRecord a short scenario, save it, run it and read its report, in about ten minutes.
Create a test
- Record a testWhat to record, the countdown, the recording toolbar, and habits that make a test reliable.
- Create a test from a promptDescribe the workflow to Claude, ChatGPT or a local AI model we provide or you bring, and it records, verifies and runs the test on your screen, edits an existing test in place, or makes one from a Figma design.
- Choose what a test verifiesThe question after every recording: visual elements, text, and what appears on screen.
Edit in GUI Test Studio
- A tour of GUI Test StudioWhere everything is: the panels, the preview, the properties and the timeline.
- Work on the timelineSelect, move, trim, copy, name and annotate the steps of a test, with undo for everything.
- Events: what a test doesClicks, typing, scrolling, drag and drop and the Test Flow steps: add them, edit them in plain words, change several at once.
- Test Flow: waits, apps, phones and scriptsPause the run, open a web app, hand a file to a page, take the network away, start or close an application, connect a phone, or run a Python script at any moment.
- Test a feature before it existsImport pictures from your design tool and prepare the test while the feature is still being built.
- Pictures, screenshots and the collageTake a screenshot, capture a frame, rename your pictures, and lay a picture over the screen to prepare a check.
- Import a design from FigmaTurn a Figma design into reference pictures and ready-made checks, and sync them when the design changes.
- Scenarios: reuse groups of stepsGroup steps like "Sign in", nest them, and add one test inside another.
Checks
- Choose the right checkNine checks, one question: what do you want to be sure of?
- Visual checksCheck that an element is there, gone, or there a given number of times.
- Text checksCheck words, values that change, missing text and how often a text appears.
- Layout and group checksCheck where things stand, or several checks of one screen at once.
- Timeouts, search areas and failuresThe settings every check shares, and what happens when one fails.
Run and read the results
- Run a testStart a run, stay hands off, stop it at any moment, or run from the middle of a test.
- Read the Confidence ReportWhat passed, what failed, why, and how close each check came.
- When the app changes on purposeAccept a new look in one click, or edit the check, so the test follows your app.
- Create a bug reportTurn a failed run into a filled-in bug report, as a PDF or a spreadsheet.
- AI Smart VerificationThe AI side of the GTS Engine + AI: a second look at a failed check, with the final verdict and an explanation in plain words.
- Enhanced Accuracy Pass (advanced)Which moment of the run a visual check is compared on, and how far it looks.
- Several looks for one checkGUI Test Studio keeps one expected version per browser, theme, screen or language, and each run uses the one you choose.
Automate
- Every browser and device from one recordingRecord a web test once and run it in Chrome, Edge and Firefox, on phones, tablets and screen sizes, in other languages and on slow networks.
- Run tests in your pipelineThe command-line runner, the results your CI tool reads, and ready-made examples.
- Web, phones, virtual machines and gamesAnything you can see on a Windows screen: how to test each kind of app.
Your account
Help
- Good practicesNames, Scenarios, notes, a description and a dedicated test environment: what makes tests last.
- Settings worth knowingThe few settings that change how tests behave, and where to find them.
- TroubleshootingA test that fails on another machine, an element not found, text not read: what to do.
- GlossaryEvery word the apps use, in one plain sentence each.
Quick answers
The questions testers ask most.Each one opens the guide that answers it.
Can't find it?Ask us: we answer within one working day.Contact support