Test runs
A test run is an execution cycle for one project. When you create a run, the system creates test run results — one row per selected test case.
Fields
| Attribute | Type | Rules |
|---|---|---|
test_run_name | string | Max 500 characters |
test_run_description | HTML | Max 2500 characters |
test_run_status | enum | See below |
assigned_to | user id | Optional — default assignee for new results |
project_id | id | Required |
created_at, updated_at, completed_at | timestamps | completed_at set when run is finished |
Run statuses
| Status | Meaning |
|---|---|
PENDING | Created, not started |
IN_PROGRESS | Execution ongoing |
COMPLETED | Finished successfully |
CLOSED | Closed without further work |
Setting status to COMPLETED or CLOSED sets completed_at. Returning to PENDING or IN_PROGRESS clears it.
Creating a run
- Open Test runs for a project → Create.
- Enter name and description.
- Choose cases:
- Pass a list of
test_case_ids, or - Use
ALLto include every case in the project, or - Omit selection — backend defaults to all project cases.
- Pass a list of
- Optionally set assigned_to for the run (copied to new results when adding cases).
Each selected case gets a test run result row in status PENDING.
Adding cases later
Use Add test cases on an existing run with test_run_id and test_case_ids. New results are created; if the run has assigned_to, it is applied to new results.
Tasks
There is no separate “testing task” table. The Tasks page (/web/{locale}/todo/listing) aggregates items assigned to you:
| Bucket | Includes |
|---|---|
| Test runs | Runs assigned to you with status PENDING or IN_PROGRESS |
| Test run results | Results assigned to you with status PENDING or IN_PROGRESS |
| Test cases | Cases assigned to you with status PENDING or IN_PROGRESS |
Optional filter: project_id.
Use Tasks as your work queue during a cycle; update test run results as you execute.
Related
| Version | 1.0 |
| Last updated | 2026-06-06 |