ATP360 Glossary
This page defines the terms used across the ATP360 knowledge-base articles. It is for anyone reading the ATP360 documentation; other articles link here rather than repeating definitions.
Terms
| Term | Meaning |
|---|---|
| CUA | Computer-using agent. The AI that actually drives the desktop — moving the pointer, clicking and typing. |
| CUA worker | A Windows machine, physical or virtual, running the ATP360 Worker agent, on which tests execute. |
| Parser | Layer 1 of the pipeline. Turns documents, videos and prompts into structured test cases. |
| Orchestrator | Layer 2. Decides which actions are needed to satisfy each test step. |
| Execution | Layer 3. Drives the CUA on the worker, turning intended actions into real clicks and keystrokes. |
| Test case | A reusable, structured set of steps with expected outcomes and pass/fail criteria. |
| Test run | One execution of a test case on one worker, with its own result, cost and audit trail. |
| Step | One instruction in a test case, with an action and an expected outcome. |
| Action | One thing the agent does — a click, a keystroke sequence, a screenshot. A step usually takes several. |
| Turn | One full cycle between the orchestrator and the CUA worker. |
| Gate | A double-check by a second, smaller model that the actions taken match the step that was asked for. How often it runs is set by Gate every N steps on the Limits & Controls tab. |
| Override | A human changing the AI’s verdict on a run, with a reason and notes. |
| Pairing key | The one-time key that binds a newly installed worker to your workspace. |
| Secret | A credential held in Azure Key Vault and inserted into a test deterministically, never seen by an AI engine. |
Related articles
- Administration Guide – Overview
- Limits & Controls — Gate every N steps
- CUA Workers — pairing key
- Stored Secrets — secrets