Execution Burndown Report

AIO Tests allows you to view a graphical representation of the total number of cases left to be executed and the total time it will take to execute them. This can be done through the burndown report. Having such a visual representation of the most important data with respect to testing will help everyone in your team to be on the same page.

In this documentation, you’ll understand:

1 Steps to Generate Execution Burndown Report
2 Execution Burndown Report Output - Overview

Steps to Generate Execution Burndown Report

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

Step 2: Once you click on the chevron icon, the Execution Burndown Report input window will be displayed on the screen. Click on the Cycle field and select a cycle for which you want to generate the Execution Burndown 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).

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.

If you have not created a plan for the cycle, the report will show a straight line in the graph indicating that the test cases will be executed in a consistent manner.

Execution Burndown Report Output - Overview

Here’s a detailed explanation of the Execution Burndown report output.

Cycle Overview

The first section of the Execution Burndown report consists of the title, objective, start date and end date of the cycle.

Burndown Chart

A sample burndown chart for a completed iteration is shown below.

The key parameters of the report are explained in the table below.

X-Axis	The Dates - according to cycle/iteration timeline.
Y-Axis	The Case Count - shows the number of cases in the cycle.
Start Point	This is the extreme left point of the chart and occurs at day 0/ start date. On hovering over, you can see how many cases are still pending in the cycle.
End Point	This is the extreme right point of the chart and marks the end date (the end date considers the day’s 6 pm as the actual end). On hovering upon, you can see that 0 cases are still pending in the cycle.
Guideline	This is a straight grey line that connects the start point to the endpoint. At the start point, the guideline shows the number of cases that are still to be executed. At the endpoint (the end date considers the day’s 6 pm as the actual end), the guideline intercepts the x-axis showing that there is no work left to be completed.
Burndown line	The blue line represents the burndown. The burndown line tells you how fast you are burning down the work. At the start point, the burndown line starts from the same point where the guideline started. But as time progresses, the burndown line fluctuates above and below the guideline depending on the pace at which the cases are being executed.

The guideline will not be shown if one or both dates are missing.
The guideline will appear only if the specified cycle in the input does not have a plan.

The goal of a burndown chart is to display the progress towards completion and give an estimate of the likelihood of timely completion. The following table shall help you measure the performance of your project.

Burndown line is above the Guideline	If the burndown line is above the guideline, it means that there is more work left than originally predicted and the project is behind schedule.
Burndown line is below the Guideline	If the burndown line is below the guideline, it means that there is less work left than originally predicted and the project is ahead of schedule.

Tabular form of Burndown Chart

The tabular form of the same burndown chart shown above can be seen in the below screenshot.

The above table shows the clickable number of cases that have been passed or failed at the Cycle’s Start date (Start point) followed by the dates on which cases were executed. It also shows how many cases are pending for those dates.

The Day Total column shows the number of cases passed or failed on a specific day.
The Cumulative Total column is the total (sum) of all of the cases remaining at the end of the day along with the previous day’s cases.

Two observations can be made from the table above:

125 cases were pending on the start date, 10 cases passed on Sep 18th and 1 failed, 17 cases passed and 0 failed on Sep 19th. So pending cases are reduced by 28 (10+1+17), which means actual pending cases are 97.
As 17 cases passed on Sep 19th (referring Day Total column), the cumulative total column adds the previous day’s 10 passed cases to this 17, to get 27 passed cases. Similarly, 0 cases failed, on Sep 19th, the cumulative total column adds the previous day’s 1 failed cases to 0 failed on Sept 19th, to get 1 failed case.

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