Glossary
The user-facing terms used in Certyn docs, and how they map to API objects.
This documentation uses Runs and Issues as the primary user-facing terms. The REST API still uses lower-level object names like tickets, executions, and testcases.
Core terms (docs)
| Term | Meaning |
|---|---|
| Project | A single application or service you operate Certyn against. |
| Environment | A named target for testing (staging/prod/etc) with its own base URL, variables, and model configuration. |
| Wiki | The context you provide to the autonomous QA team: product overview and non-negotiable rules. |
| Test | A reusable check (natural-language test case) that can be run repeatedly. |
| Process | A suite definition: which tests to run (usually by tags), how to schedule them, and what should trigger runs. |
| Run | A single execution of a process (or an ad-hoc task) that produces artifacts and outcomes. |
| Issue | A work item created from failures or exploration, backed by evidence and linked to runs/sessions. |
| Session | An isolated agent runtime (container + browser) that performs a unit of work and records artifacts. |
Mapping to API objects (precision)
| Docs term | API object(s) | Notes |
|---|---|---|
| Run | Ticket (type TestRun) + execution entities | Runs are tracked as tickets for auditability. |
| Issue | Ticket (type Issue) | Issues can be created by failures or manually. |
| Test | TestCase | Tests may be human-authored or AI-generated (often needing review). |
| Session | AgentSession | Sessions are the live browser sessions you can watch. |
| Process | ProcessDefinition | Processes define schedules, tags, and triggers. |
If you prefer API-native language, you can read "Run = Ticket (TestRun)" and "Issue = Ticket (Issue)" throughout the docs.