Glossary
The terms used across the Astra Scout docs, each in one or two sentences.
Terms used across the Astra Scout docs, in alphabetical order.
Build
One uploaded version of the app: an .ipa, an .apk or a simulator .app. Testers pick a build in the Builds window and install it on a device. See Builds.
Catalog
The list of analytics events an app must send, with their properties, allowed values and general rules. One file per app: tracking-specs/<app>.yaml. See Tracking catalog.
Conflict
A file that changed on this Mac and in the cloud since the last sync. Team Sync keeps syncing the other files and asks you which version to keep. See Conflicts.
Environment
A named set of variables and tags applied to a run. Use it to run the same flow against different accounts, builds or servers without editing the YAML. See Environments and variables.
Event
One analytics record the app sends, for example Paywall Viewed, with its properties. Astra Scout receives the events of a QA build during a run and checks them against the catalog and the flow.
Flow
A YAML file that describes one test: which app to open and what to tap, type and check. See Flows.
Launch argument
A value passed to an iOS app when it starts. iOS stores it in UserDefaults, where the app's code can read it. Astra Scout passes scoutServerUrl this way.
MCP
The channel an AI CLI (Claude Code, Codex CLI, Gemini CLI) uses to call Astra Scout's features. Turn it on in Settings > Intelligence > MCP Connection. See The scout plugin.
QA build
The build of the app that testers install. It sends its analytics events to Astra Scout instead of Amplitude. The release build is not changed. See Send QA build events to Astra Scout.
Revision
One saved version of a synced file. Every save that reaches the cloud is a revision. History lists them and can restore one. See History and Restore.
Rule
A check in the catalog that is not tied to one event, for example "paywall id must be the same in Paywall Viewed and Paywall Skipped". Each rule has a severity. See General rules.
Run
One execution of a flow on a device. Every run is saved with its steps, video, events and verdict, and is listed under Test Runs.
scoutServerUrl
The launch argument that holds the address of Astra Scout on the tester's Mac. Astra Scout passes it each time a flow opens an iOS app with launchApp. The QA build uses it as the Amplitude serverUrl.
Selector
The part of a command that says which element on screen to act on, for example by its text or id. See Selectors.
serverUrl
The Amplitude SDK option that sets where events are sent. The QA build sets it to Astra Scout's address.
Severity
How much a failed check counts. Error fails the check and the run. Warning is recorded in the report and the run does not fail. Ignore turns the check off. See Severities.
Step
One command in a flow, for example tapOn or assertVisible. A run shows pass or fail for each step.
Taxonomy
The team's event plan, usually kept in a spreadsheet. Astra Scout imports it into a catalog. See Import your taxonomy.
Team Sync
The feature that keeps one workspace the same on every teammate's Mac through the team's cloud. See Team Sync.
UDID
The unique id of an iOS device. A development or Ad Hoc build installs only on iOS devices whose UDID is in its provisioning profile. Astra Scout sends the UDID of a tester's iOS device to the team so an owner can register it. See When the iOS device is not in the profile.
User property
A value Amplitude keeps on the user rather than on one event, for example the access level. The catalog lists user properties and their rules. See User property rules.
Workspace
The folder Astra Scout opens. It holds your flows and the tracking catalogs in tracking-specs/.