Executions
Overview
Each execution records the result of running a single test case. Executions are stored as items on the 4QA - Test Executions board and are linked back to the test case they were run against.
Recording Results
- Open an execution item view.
- The step table displays each step from the linked test case with its Expected Result.
- For each step, enter the Actual Result and set the Result column to one of: Pass, Fail, Blocked, or Skip.
- The overall execution result is calculated automatically based on the individual step results.
Auto-Calculated Overall Result
The overall result for an execution is determined by the following rules, evaluated in order:
- If any step is Fail, the overall result is Fail.
- If all steps are Pass, the overall result is Pass.
- If any step is Blocked (and none failed), the overall result is Blocked.
- If all steps are Skip, the overall result is Skip.
Execution Columns
| Column | Values |
|---|---|
| Name | Free text (item name) |
| Result | Not Run, Pass, Fail, Blocked, Skip, Retest |
| Linked Test Case | Board relation to Test Cases board |
| Assigned Tester | People column |
| Execution Date | Date column |
| Environment | Free text (e.g. staging, production, QA) |
| Build/Version | Free text (e.g. v2.4.1, build-789) |
| Duration | Numeric (minutes) |
| Defects | Board relation to Defects board |
| Notes | Free text for additional context |
Step Result Columns
Each execution step is a subitem with the following columns:
| Column | Description |
|---|---|
| Step Action | The action to perform (item name, copied from the test case step). |
| Expected Result | What should happen (copied from the test case step). |
| Actual Result | What actually happened during execution. |
| Result | Pass, Fail, Blocked, or Skip. |
| Position | Numeric order matching the test case step order. |
Creating Defects
When a step fails, you can create a defect directly from the execution. The new defect item is created on the 4QA - Defects board and automatically linked back to the execution, giving you full traceability from failed step to reported bug.