This documentation uses Runs and Issues as the primary user-facing terms. The REST API 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 Certyn: product overview and non-negotiable rules. |
| Test | A reusable check (natural-language test case) that can be run repeatedly. |
| Process | A suite definition: what to run, how to schedule it, and who executes it. See process kinds. |
| Run | One batch execution of a process. Holds one execution per test and reports pass/fail counts. |
| Execution | One attempt at one test. This is the unit that carries a status, an outcome, and its evidence. |
| Issue | A problem found by a run or filed by a person, backed by evidence and linked to the executions it came from. |
| Session | An isolated agent runtime (container + browser or device) that performs a unit of work and records artifacts. |
Mapping to API objects (precision)
| Docs term | API object | Notes |
|---|---|---|
| Run | ProcessRun | Created only by batch paths: a process run, or a CI report pushed in. Carries TotalItems, StartedAt, CompletedAt, HasFailures. Pass and fail counts are computed from its executions. |
| Execution | Execution | Every test attempt is an execution, whether or not it belongs to a run. Single-test paths (quick test, retest, running one case) create an execution with no ProcessRun. |
| Issue | Ticket | Types are bug, improvement, task, and vulnerability. issue is accepted as a legacy alias for bug. |
| Test | TestCase | Tests may be human-authored or agent-generated (often needing review). External-suite processes run cases that live in your test management tool and create no TestCase rows. |
| Session | AgentSession | The live browser or device session you can watch. Pushed CI runs have no session. |
| Process | ProcessDefinition | Carries the kind (Suite, Agent, ExternalSuite, Automation), schedules, tags, and triggers. |
Issues are linked to the executions that produced or retested them through ExecutionTicketLink, so one issue can carry its original discovery and every later retest.
Older docs said Run = Ticket
Runs used to be stored as tickets of type TestRun. That is no longer true. Runs are ProcessRun plus Execution records, and a Ticket is only ever a found issue. If you have integration code that filters tickets by a TestRun type, it needs updating.