Multi Cycle Execution Summary Report

The Multi Cycle Execution Summary report allows you to view the current status and progress of multiple cycles together. The report shows the details about the cases added to the cycles, their status, execution effort, defects, etc. for all specified cycles. For example, if you have multiple cycles for a particular release covering new features and regression, you can generate a multi-cycle execution summary report. This report includes all the cycles of that particular release and enables you to track the progression of your testing throughout each cycle.

In this documentation, you’ll understand:

Steps to Generate Multi Cycle Execution Summary Report

Step 1: To generate Multi Cycle Execution Summary Report, simply click on the Chevron option for Multi Cycle Execution Summary.

Group 1 (69).png

Step 2: Once you click on the chevron icon, the Multi Cycle Execution Summary Report input window will be displayed on the screen. Select the desired project and cycles from their respective fields for which you want to generate the Execution Summary Report. 

  • 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’.

 

 

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. 

Multi Cycle Execution Summary Report Output- Overview

Here’s a detailed explanation of the Multi Cycle Execution Summary report output. 

  • Cycle Overview

The first section of the Multi Cycle Execution Summary report consists of different statistics for the selected cycles. The statistics consist of:

  1. Cycles: The number of cycles provided as input.

  2. Unique Cases: The number of unique cases across the specified cycles.

  3. Total cases: Total number of cases to be executed.

  4. Incomplete Cases: The number of cases in In Progress, Blocked and Not Run status. The box can be clicked to check the case details.

  5. Passed Cases: The number of Passed cases in all the cycles. The box can be clicked to check the case details.

  6. Failed Cases: The number of Failed cases in all the cycles. The box can be clicked to check the case details.

  7. Estimated Effort: It is the Total effort which is calculated based on the “estimated effort” time of all cases across all cycles.

  8. Runs: Number of runs in all the cycles.

  9. Actual Effort: It is the Actual effort, which is calculated based on the “actual effort” i.e. time taken to execute/ run all cases.

  10. Remaining Est. Effort: It is the sum of the estimated effort for the incomplete cases.

  11. All Defects: The total number of defects raised in the cycles (including all the runs). The box can be clicked to check the defect details.

  12. Latest Run Defects: The number of defects associated with the latest run of cases across cycles. The box can be clicked to check the defect details.

  • Cycles Summary

The Cycles Summary section of the generated report gives details of execution for all the cycles specified in the input by using bar charts for Case distribution, Estimated Effort distribution and a table with clickable numerical details. This information can be used to see how the overall testing is progressing for a given set of cycles.

  1. Case Distribution: It shows case count by the selected cycles, broken down by the last run execution status of cases.

  2. Estimated Effort Distribution: It shows the Remaining and Completed Est. Effort for cases in each cycle. Completed estimated effort is the total of estimated effort for completed cases (cases in Passed/Failed status). Similarly, the remaining estimated effort is the total of the estimated effort for incomplete cases (cases in Blocked/In Progress/Not Run status).

  3. Detailed Execution Table: It shows the start date and end date of all specified cycles along with the clickable number of cases in each of the execution statuses, # of runs, defects, etc. The percentage values are also shown along with the count for all the Run status columns in the grid.

The user has the option to filter cycles to see the ones with pending executions (Not Run, In Progress and Blocked cases) by clicking on the “Only show Cycles with pending executions” checkbox, as highlighted in the image below.

  • Defect Summary

The Defect Summary section shows the defect summary in three ways- Defect status distribution, defect priority distribution and defect details table.

The Status Distribution pie chart (on the left-hand side) can be used to see the Defects distribution based on Status, and the Priority Distribution pie chart (on the right-hand side) to see the Defects distribution based on Priority. On hovering over these pie charts, you can view the details like status, priority and count.

The defect details table (below the pie charts) shows all the defects in rows with details like the type of the defect, its key, the title associated with the defect, its priority, status, the assigned reporter, etc. There is an option for the user to see the distribution and details for all defects found in all runs of all the cycles by unchecking the Show only the latest run defects option, as shown below. By default, it checks and shows the distribution for defects only associated with the latest runs.

Users have the option to add more columns to the defect details table by using the “Select Columns” button. Once the user clicks on the “Select Columns” button, the below screen will be displayed which allows them to add desired columns to the table. In the screenshot below, the highlighted section displays the order in which the selected columns will be shown. 

The columns selected will be stored according to the user’s preference and the same columns will be available next time when the report is generated.

Key & Summary cannot be removed from the table.

Users also have the option to view all the defects by clicking on the “Show in Issue Navigator” button. Once the user clicks on the Show in Issue Navigator button, they will be redirected to the Issues screen, where they can view the issue key, its summary, assignee, and issue reporter.

Users have the option to filter the data of the defect details table based on the data available in the table by simply clicking on the filter icon on the column level.

For further queries and suggestions, feel free to reach out to our customer support via help@aiotests.com.