Page History
Shows a list of Test Executions, their attributtes and information about overall progress and linked defects.Sets and their attributtes, along with an overview of the calculated status for the Tests that are part of the Test Set.
Purpose
The Test Executions List Report shows a list of Test Execution issues and their corresponding execution status. A Test Execution status is shown as a progress bar with the latest Test Run status from each Test issue that is associated with that Test Execution.
Possible usage scenarios:
The Test Sets List Report shows a list of Test Sets issues and their corresponding execution status, for some defined scope. A status is shown as a progress bar and is calculated based on the analysis & scope (i.e. on how you want to analyze the Tests). This allows a transversal analysis of the Tests Sets for a project in a particular version and environment.
The status of a Test Set (i.e. status of the Tests belonging to a Test Set) is calculated based on the latest consolidate results obtained for the Tests (see how the status of a Test is calculated here).
Possible usage scenarios:
- see what Test Sets exist for a project, based on some additional criteria
- quickly analyze how certain Tests belonging to some Test Sets are for some version or/and for some Test Environment
- analyze both the progress of each Test Execution and the success rate
- analyze the amount of defects opened in each Test Execution
- analyze the testing results for some revisions of the SUT
- see the planned Test Executions for some version, for some Test Environment and get an overview of the progress of each one of them
How to use
This report is accessible either from the Xray icon on the project left sidebar or from the standard Reports icon, which includes other kinds of reports besides Xray.
Source Test Execution Set issues can be directly provided using a saved filter or by specifying some Test ExecutionSet-related fields:
- Saved filter: a saved filter containing Test Execution Set issues
- Project: the project containing Test ExecutionsSets
- Fix Version: the version assigned to the Test ExecutionSet
- Assignee: the Test Execution Set issue assignee
- Component: the component assigned to the Test Execution Set issue
- Status: the Test Execution issue workflow Status
- Resolution: the Test Execution Status issue Resolution
- Test Plan: the assigned Test Plan
- Environment: the assigned Test Environment
- Revision: the revision of the SUT, which is assigned to the Test Execution
- Contains: search based on the key or the summary of the Test ExecutionSet
- Include Previous Versions: filter Test Executions Sets older or equal than the given Fix Version
| Info | ||
|---|---|---|
| ||
Only Test Executions Sets from the selected project are shown by default. For showing Test Executions Sets from different projects you have to use a saved filter. |
...
Besides all available custom fields for Test Execution Sets issues, there are also some special columns that can be included:+
Metric | Notes |
|---|---|
| The revision of the SUT targetted by this Test Execution (i.e. typically the code revision or the build number) | |
| Begin Date | Planned begin date for the Test Execution |
| End Date | Planned end date for the Test Execution |
| Test Environment(s) | Test Environment(s) linked to the Test Execution (i.e. the environment assigned to the Test Execution where tests were executed on or are schedule to be executed on) |
Defects | Amount of linked defects (i.e. the ones created/linked during execution of tests) |
| Status | The progress (i.e. the overall execution status of the Test Execution) |
Example
| Test Count | Amount of Tests within each Test Set |
|---|---|
| Status | The calculated status for the Tests that are part of the Test Set, based on the defined Analysis & Scope |
Example
