Glossary
Every word the apps use, in one plain sentence each.
Every term, A to W
Click a term to read more about it.
- Accessibility informationWhat an application tells Windows about its elements: their names, roles and places, the same information a screen reader uses.The GTS Engine asks it first to find an element.
- AI InstructionsYour own words for one check, such as "ignore the font size", which AI Smart Verification follows when it judges that check.
- AssertA check: a moment where the test makes sure something is right on the screen.
- BaselineOne check's expected version, or one step's own settings, for one environment: a dark-mode look, the words a step types in French, another address.
- Baseline profileA named environment, such as "Dark mode" or "French", whose versions the checks can hold.
- BranchA version of a recorded web test for another browser, device, orientation or condition, made by GUI Test Runner-Recorder.
- BlockOne step on the timeline: a click, a typed text, a check.
- Confidence ReportThe report a run produces: every step, every check, what was expected and what was found.
- ConnectorWhat lets an AI assistant, Claude Desktop, Claude Code, ChatGPT with Codex or VS Code, record, edit and run tests through GUI Test Studio.
- Count ruleWhat a count check holds the total to: exactly, at least, at most, or between two numbers.
- Dynamic Text AssertA text check that waits for a kind of value (a date, an amount) rather than a fixed value.
- Go Offline, Go OnlineTest Flow steps that cut the network at a moment of the test and give it back.
- gtr-cliThe command-line runner: runs tests without a window, for scripts and CI/CD pipelines.
- Group AssertSeveral checks of one screen, run together as one block.
- GTS Engine + AIThe engine behind every check.It finds each element through the application's accessibility information, or by sight when the application does not say, then compares it with what you expect.Its optional AI side is AI Smart Verification.
- HeadlessA run without a browser window: the page works out of sight and the computer stays yours.
- HistoryEvery run of a test, kept with it, to see when a check started failing.
- Layout AssertA check of where the elements of a screen stand, not of how they look.
- Local AI modelAn AI model that runs on your own computer, one we provide in GUI Test Studio's built-in engine or one you bring through LM Studio or any OpenAI-compatible local server: it can create a test from a prompt, and explain a failed check, with nothing leaving the computer.
- Machine keyA key that signs a build agent in, for a computer nobody sits at.It takes one seat.
- MarkerA note on the timeline for you and your team; never part of a run.
- MemberA person who uses the apps under the plan of a team's owner, with an account of their own.
- Move Mouse ToA text check's option that aims the clicks after it at the text it found.
- OwnerThe person who pays for a plan and shares its seats with a team.
- PlayheadThe red line on the timeline: the moment shown in the preview.
- Practice pageThe small sign-up form that comes with the app, on which the Getting Started Guide makes your first test.
- Project SettingsThe settings of one test, which travel with it.
- Prompt (Create Test From Prompt)The second way to create a test: describe it in words, and your AI assistant records, verifies and runs it on your screen.Claude, ChatGPT or a local AI model: one we provide, or one you bring.
- Properties panelGUI Test Studio's panel that shows everything about the selected block, in tabs, ready to edit.
- RunOne replay of a test on the live screen.
- Run On, Record OnOn a computer with several monitors, the screen a test runs on, or a recording uses: one monitor or all of them.
- Runs cardThe list of a test's past runs on its page in GUI Test Runner-Recorder; a double-click opens a run's report.
- Runner test (.GTR)A test exported without its recording: smaller, for running only.
- ScenarioA named, coloured group of steps, such as "Sign in"; also how one test is added inside another.
- SeatOne person on one computer.A plan has one seat per user.
- Search area (Search Scope)The part of the screen where a check looks for its element.
- Search Entire ScreenA check's option to look everywhere on the screen.
- Search PhaseThe first step of a visual check: finding the element on the screen.
- Search SensitivityHow sure the GTS Engine + AI must be before it says an element is found.
- TeamThe people who share one plan: its owner and the members they invited.
- Test (.GTS)A test file: its steps, its checks and its recording.
- TimeoutThe longest a check waits for what it expects.
- TrackA row of the timeline holding one kind of step: mouse, keyboard, checks.
- Upload FileA Test Flow step that hands files to a web page, without the system's file window.
- Verification PhaseThe second step of a visual check: comparing what was found with the recorded picture.
- Verification StrictnessHow strict that comparison is: Exact, Strict, Standard or Relaxed.
- Visual ReferenceThe track that holds the recording, for you to see the screen at every moment.
- Visual targetThe picture of the element a visual check looks for.
- WaitA pause of a fixed length in the run.
- Weakest linksThe checks that passed by the smallest margin: the ones most likely to fail next.
Still stuck?Tell us what you were trying to do, and we answer within one working day.Ask our team