Page History
Shows a list of Test Executions, their attributtes and information about overall progress and linked defects.Sets and their attributes, along with an overview of the calculated status for the Tests that are part of the Test Set, for the selected version or Test Plan, and/or Test Environment.
Purpose
The Test Executions Sets List Report shows a list of Test Execution Set issues and their corresponding execution status. A Test Execution , for some defined scope. The status is shown as a progress bar with the latest Test Run status from each Test issue that is associated with that Test Executionand 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 consolidated 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 doing, 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 issues can be directly provided using a saved filter or by specifying some Test Execution-related fields:
At the top of the report, you have some options that need to be configured.
- Analysis & Scope: how to analyze the issues (more info on Coverage Analysis)
- Filters: the source data for the report (e.g. Test Set issues) and how to evaluate the status for each one of the item being shown.
- Advanced: a JQL query to filter the coverable issues
- Basic:
- Project: project
- Assignee: the issue's
Saved filter: a saved filter containing Test Execution issues - Project: the project containing Test Executions
- Fix Version: the version assigned to the Test Execution
- Assignee: the Test Execution issue
- assignee
- Component: the component assigned to the
- issue
- Fix Versions: versions assigned to the
- issue
- Resolution: the
- 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 Execution
- Include Previous Versions: filter Test Executions older or equal than the given Fix Version
- workflow resolution
- Status: the workflow status
- Contains: the full issue key or part of the summary
| Info | ||
|---|---|---|
| ||
Only Test Executions By default, only the Test Sets from the selected project are shown by default. For showing Test Executions . To show the Test Sets from different projects, you have to use a saved filter. |
Columns
Besides all Aside from the available custom fields for Test Execution Sets issues, there are also some special columns that can be included:+
Metric | Notes |
|---|---|
| RevisionTest Count | 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
| Number 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
Exporting the Report
The report can be exported to a CSV file, which will export up to 1000 issues and not just the visible ones.
Click on Export and select To csv.
Share
To share the report click the Share button and then click the copy icon to copy the link to clipboard after this you can send the link to other users who can then view the report with the same filters. This link will be deleted if it's not used for more than 6 months.
