Test run results
A test run result is the execution record for one test case inside one test run. When you create a run, the system generates one result per included case.
Fields
| Attribute | Type | Notes |
|---|---|---|
test_run_id | id | Parent run |
test_case_id | id | Case being executed |
test_result_status | enum | Outcome — see below |
assigned_to | user id | Optional tester |
created_at, updated_at, completed_at | timestamps | Completion time set for terminal outcomes |
Result statuses
| Status | Meaning | completed_at |
|---|---|---|
PENDING | Not executed yet | Cleared |
PASSED | Test passed | Set |
FAILED | Test failed | Set |
SKIPPED | Not run (out of scope) | Cleared |
BLOCKED | Cannot run (blocker) | Set |
RETEST | Needs another attempt | Cleared |
Performing testing
- Open the test run (listing → details).
- Walk through each result (linked to its test case and steps).
- Set the result status as you go.
- When all results are done, set the test run status to
COMPLETEDorCLOSED.
Assignment: if you are assigned_to, the item appears under Tasks.
Manual execution only
Complex QA does not generate automated execution reports today. Status changes are manual through the UI or API (/web_api/test_run_result/update_property).
Step-level UI metadata (clicks, selectors) on cases is for documentation and future automation, not live test runners.
Related
| Version | 1.0 |
| Last updated | 2026-06-06 |