Page History
...
Possible usage scenarios:
- see all the Test Run Status overall status for a given Test Plansee the status of Test Runs in a Test Plan and understand what happened, considering the consolidated results for the Tests being tracked
- track the planned Test Plans that are taking most timefor a release
Output Example(s)
The following table shows an example of the columns/rows you should expect.
...
| Code Block | ||
|---|---|---|
| ||
project = "EWB" and issuetype = "Test Plan" order BY created DESC |
...
| Code Block | ||
|---|---|---|
| ||
project = "EWB" and issuetype = "Test Plan" and fixVersion=1.2 order BY created DESC |
...
| Code Block | ||
|---|---|---|
| ||
project = "EWB" and issuetype = "Test Plan" and testEnvironments = chrome order BY created DESC |
...
| Column | Notes |
|---|---|
Key | Issue key of the Test Plan |
| Summary | Summary of the Test Plan |
| Fix versions | The fix versions defined in the Test Plan |
| Begin Date | Timestamp of when the Test Plan started, in the format "dd-MM-yyyy hh:mm:ss" |
| End Date | Timestamp of when the Test Plan ended, in the format "dd-MM-yyyy hh:mm:ss" |
| Test Run Status | The overall status, including the number of tests that are part of the Test Plan and the consolidated status of the latest test run executed for this Test Plan. You have the results divided by for each test. A percentage is also provided for the different statuses (e.g., PASSED, FAILED, EXECUTING, TO DO, and ABORTED). |
Customizing the report
Adding or removing information to/from the report
...
| Info | ||
|---|---|---|
| ||
|
Known limitations
- Test Run Status The overall status provided on the Status column is not formatted in a machine friendly-format