Automation Coverage Report
The Automation Coverage Report allows managers to view details about the automated cases against the manual cases. With the help of this report, you can measure and compare the savings in effort due to automation testing. This report allows you to specify cases for which automation coverage can be seen across multiple parameters.
In this documentation, you’ll understand:
Steps to Generate Automation Coverage Report
Step 1: To generate Automation Coverage Report, simply click on the Chevron option for Automation Coverage.
Step 2: Once you click on the chevron icon, the Automation Coverage Report input window will be displayed on the screen. Select the desired Case Selection Criteria from the given options- Cases, Sets, Cycles, and Requirements. With each case selection criteria, there is an option to select multiple projects in the Projects field and specify a parameter- “Distribution By,” using which the automation coverage will be shown.
Cases: Users can specify a list of cases by using the filter option or keep it empty to select all cases of the project. The default distribution is shown by ‘Automation Owner’ but users can choose any of the available options.
Sets: Users can specify a list of sets by using the filter option. The automation coverage report will be generated for unique cases belonging to specified sets. The default distribution is shown by ‘Sets’, but users can choose any of the available options.
Cycles: Users can specify a list of cycles by using the filter option. The automation coverage report will be generated for unique cases belonging to specified cycles. The default distribution is shown by ‘Cycle’ but users can choose any of the available options.
Users can also use the filter option to narrow down the Cycles list. They can filter the Cycles list by Component, Release, Cycle Tags, Folders, or any custom fields (which can be added via the inverted triangle icon).
Users also have the option to specify a dynamic filter for cycles by changing ‘List’ to ‘Filter.’
Users can select the Exclude Archived Cases checkbox to exclude the archived cases from the generated report.
Requirements: Users can specify a list of requirements by specifying Jira issue IDs, by using JQL or by using Jira’s saved filters. The automation coverage report will be generated for cases linked to the specified requirements. The default distribution is shown by ‘Requirement’ but users can choose any of the available options.
Step 3: Finally, click on the Generate button.
Users can also save reports to reuse them later by clicking on the Save button.
Once you click on the Generate button, the report output will be displayed on the screen.
Automation Coverage Report Output- Overview
Here’s a detailed explanation of the Automation Coverage report output.
Overview
Here’s a detailed explanation of the Overview section:
Total Cases: It shows the total number of cases as per the selection criteria (excluding the draft cases of other users).
Automated: It shows the number of automated cases (based on Automation Status = Automated)
Non-Automated: It shows the number of cases yet to be automated (based on Automation Status != Automated).
Total Effort: Sum of estimated effort of all specified cases.
Effort Savings: It is the sum of the estimated effort of automated cases.
Manual Effort: Sum of estimated effort of non-automated cases.
If the user does not have access to some cases, all fields will only reflect accessible case data.
Distribution
The distribution pie chart shows the cases in different Automation statuses namely Automated, In Progress, to be Automated, Manual and Not Assigned. On hovering over each slice of pie, the status count can be seen.
Coverage Details
The coverage details section shows a quick summary of the automated cases with respect to the distribution parameter given in the input criteria. The grid columns are divided into two sub-categories- Automation Status and Effort.
For further queries and suggestions, feel free to reach out to our customer support via help@aiotests.com.