Our documentation site has been updated to AIO Tests Knowledge Base
Execution Burndown Report
- Noopur Varshney [AIO Tests]
AIO Tests gives you the opportunity to view graphical representation of how many cases are left to be executed and how much time will it take to execute them. This can be done through our burndown report.
Having such visual representation of most important data with respect to testing, will help everyone in your team, to be on the same page.
Generating Execution Burndown Report
Click on the right chevron, next to the execution burndown report to view the input screen for the report. In the Cycle field, select a cycle for which you want to generate the Execution Burndown Report. Clicking on Generate will generate the report. The filter option can be enabled to narrow down the cycles list. You can filter the cycles list by Component, Release, Cycle Tags or by Cycle Folders.
The below screenshot shows the output of Execution Burndown Report for a cycle.
Each section of the report is explained below.
Cycle Overview
The top section 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. 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 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 upon, 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 0 cases are still pending in the cycle. |
Guideline | This is a straight grey line that connects the start point to the end point. At the start point, the guideline shows the number of cases that are still to be executed. At the end point (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 same point where 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. |
Please note that the guideline will not be shown if one of or both the dates are missing
The goal of a burndown chart is to display the progress toward completion and give an estimate on the likelihood of timely completion. The following table shall help you measure 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.
This table shows number of cases that have been passed or failed at on 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 in the specific day.
The Cumulative Total column is the total (sum) of all of the cases remaining at the end of the day along with previous day’s cases too.
Two observations can be made from the table above:
186 cases were pending on start date, 9 cases got passed and 2 got failed on July 14th. So pending cases reduces by 11 (9+2), which means 175.
As 21 cases were passed, on July 14th (referring Day Total column), the cumulative total column adds previous day’s 9 passed cases to this 21, to get 30 passed cases. Similarly, 12 cases were failed, on July 14th, the cumulative total column adds previous day’s 2 failed cases to this 12, to get 14 failed cases.