Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

AIO Tests allows you to view a graphical representation of the total number of cases executed compared to the planned test cases and the total time it took to execute them. Having such a visual representation of the most important data with respect to testing will help everyone on your team be on the same page.

Steps to Generate Execution Burnup Report 

Step 1: To generate the Execution Burnup Report, all you need to do is click on the Chevron option for Execution Burnup.

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

If you have not created a plan for the cycle, the report will show a straight line indicating that all the test cases are executed in a consistent manner. (Shown below) or you can add a downward arrow mark

Execution Burnup Report - Overview

Here’s a detailed explanation of the Execution Burnup report. 

  • Cycle Overview

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

  • Burnup Chart

A sample burnup 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 the 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 completed in the cycle.

End Point

This is the extreme right point of the chart and marks the end date. On hovering upon, you can see that 125 cases are completed in the cycle.

Actual Scope

This is a straight orange line showing the actual number of cases that should be completed in the timeline.

Planned 

The grey line represents the number of planned cases for each day. 

Burnup line

The blue line represents the burnup. The burnup line tells you how fast you are completing the work. At the start point, the burnup line starts from the same point where the guideline started. But as time progresses, the burnup line fluctuates above and below the guideline depending on the pace at which the cases are being executed.

  • Tabular form of Burnup Chart

A tabular form of the same burnup chart  can be seen below :

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 were completed on those dates.

  1. The Day Total column shows the number of cases passed or failed on a specific day.

  2. The Cumulative Total column is the total (sum) of all of the cases completed at the end of the day, along with the previous day’s cases.

    Two observations can be made from the table above:

  • 0 cases were completed on the start date, 10 cases passed on Sep 18th and 1 failed, 17 cases passed, and 0 failed on Sep 19th. So, completed cases are increased by 28 (10+1+17), which means actual completed cases are 28. 

  • 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 dedicated support via help@aiotests.com.

  • No labels