Page History
...
Possible usage scenarios:
- see all the Test Run Statuses statuses count for a given Test Execution
- see the linked Test Plans and Defects
- track the Test Executions that are taking the most time
...
Column | Notes |
---|---|
Key | Issue key of the Test Execution |
Summary | Summary of the Test Execution |
Fix versions | Fix versions version(s) defined in the Test Execution |
Revision | Revision defined in the Test Execution |
Begin Date | Timestamp of when the Test Execution started, in the format "dd-MM-yyyy hh:mm:ss" |
End Date | Timestamp of when the Test Execution ended, in the format "dd-MM-yyyy hh:mm:ss" |
Test Environment | Test Environments Environment(s) defined in the Test Execution |
Test Plan | Test Plans Plan(s) linked to the Test Execution |
Defects | Defects linked to the Test Execution (at either the test run or the test step level) |
Status | The number of test runs that are part of the Test Execution and their latest status. You have the results divided by PASSED, FAILED, EXECUTING, TO DO, and ABORTED |
...
Info | ||
---|---|---|
| ||
|
Known limitations
- Test Run Status Execution overall status shown on the Status column is not formatted in a machine-friendly layout