Element reference
Test run result
Test run result
A test run result is the execution record for one test case inside one test run.
Relations
| Related element | How it connects |
|---|---|
| Test run | Required parent (test_run_id) |
| Test case | Case being executed (test_case_id) |
| Bug | Optional links on the result Bugs tab |
| Assignee | Optional tester (assigned_to) |
Fields
| Label | Technical name | Type | Required | Validation | Default |
|---|---|---|---|---|---|
| Run | test_run_id | id | Yes | - | - |
| Case | test_case_id | id | Yes | - | - |
| Status | test_result_status | enum | Yes | See enumerations | PENDING |
| Assignee | assigned_to | user id | No | Can be cleared with Not assigned | - |
| Notes | test_result_description | text | No | Free-text comments on this execution | - |
Enumerations
Status (test_result_status)
| Value | Meaning | completed_at |
|---|---|---|
PENDING | Not executed yet | Cleared |
PASSED | Test passed | Set |
FAILED | Test failed | Set |
SKIPPED | Not run | Cleared |
BLOCKED | Cannot run | Set |
RETEST | Needs another attempt | Cleared |
The mark next to a status uses the shared status color. SKIPPED is not the same color as BLOCKED. BLOCKED is not the same color as a closed test case.
Rules
- Delete removes the result from the run. The case in the catalog stays.
- If you are
assigned_toon an open result, the item appears under Tasks.
Limits
- Status changes are manual in the UI or through the API. ComplexQA does not write automated execution reports for manual test run results.
Did this page help?