Glossary

Quick reference for the vocabulary used across the rest of this manual.

AI Segmentation

How Mavster processes the screen for a step. Three modes: None, Auto, Force Fresh. The picker appears in Tap and Scroll editors. → AI Segmentation modes

Assert Memory

The Visual Assert memory toggle. Remembers the assertion target between runs and validates before reuse. On by default. → Assert Memory & List Bounds Memory

Assertion

A pass/fail gate. In Mavster, almost always a Visual Assert step that checks the screen against a plain-language description. → Visual Assert

Conditional child

A nested step under another step that runs only when the parent step's status matches its "run on" mode (success or failure). Only one level of nesting is supported. → Tests, Suites, and Steps

Credit check

The credit and subscription check that runs before every test. Three outcomes: pass, insufficient credits, subscription required. → Credits & cost preflight

Hard failure

A test outcome distinct from a regular step failure — set when the test was blocked before it could run (e.g. credit check failed, simulator couldn't be reserved). → Reading results & history

Healing incident

The full self-healing lifecycle for one failed step — captured snapshot, AI planning, recovery actions, and final outcome (healed or exhausted). → Self-healing

Instance (User-Defined)

A copy of a User-Defined template embedded in a test. Editable in place; future template edits propagate unless overridden locally. → User-Defined Templates vs. Instances

List Bounds Memory

The Scroll memory toggle. Remembers the bounds of the scrollable region across runs so Mavster doesn't re-detect from scratch. On by default. → Assert Memory & List Bounds Memory

Local override

A step inside a User-Defined instance that you've edited locally. Future template edits skip locally-overridden steps. → User-Defined Templates vs. Instances

Memory

Catch-all for the three memory toggles: Position Memory (Tap), Assert Memory (Visual Assert), List Bounds Memory (Scroll). All validate before reuse. → Position Memory and Assert Memory & List Bounds Memory

Parameter / $placeholder

A $variable in a step instruction, Scroll's "Until" field, or test name. Substituted at run time from a Run Test step's arguments or a User-Defined instance's arguments. → Parameters & $placeholders

Position Memory

The Tap memory toggle. Remembers the resolved tap coordinate between runs and validates before reuse. On by default. → Position Memory

Project

Top-level container for tests, suites, run history, costs, and project settings. Syncs to the cloud as a unit when Cloud Sync is on.

Region of Interest

A subregion of the screen used to narrow the search. Choose from full screen, content area, top/bottom navigation, top/bottom third, plus leading/trailing/center variants. → Region of Interest

Run Test

The interaction that calls another test by name. Supports arguments for parameter substitution and a Run Count override. → Run Test

Self-healing

Opt-in recovery mechanism. Three modes: Strict (off), Per Step, Full Test. Tier-gated to Ultra. → Self-healing

Step

A single action in a test — one of the ten interaction kinds. → Tests, Suites, and Steps

Suite

A folder for grouping tests. Tests can belong to multiple suites or none. → Suite management

Template (User-Defined)

The master, global record of a User-Defined sequence. Available across every project on your Mac. → User-Defined Templates vs. Instances

Test

An ordered list of steps with a name, a Run Count, and a self-healing mode. Stops on the first failed step unless that step has a "run on failure" branch.

Toolbox

The palette of ten interaction kinds (plus the User Defined section listing your templates) on the left of the editor. → The Toolbox