Our documentation site has been updated to AIO Tests Knowledge Base

Case Distribution Report

Overview

Case Distribution Report enables Users to analyze the Case data by grouping & aggregating by different parameters. Users can choose to group the data either by single parameter to see the report in list form or group by two parameters to see the report in matrix form. Since report allows selection of grouping parameters and aggregator method, report can be generated to help in analysis of number of scenarios.

Refer to the example to get idea on how to use this report.

Generating Case Distribution Report

From the Report listing page, click on the right chevron next to the Case Distribution report to get the input screen for the report.

 

There are 4 ways (Cases, Sets, Cycles & Requirements) for users to select the cases for the report. With each cases selection criteria, there are options to select “Primary Group By“ (mandatory), “Secondary Group By“ (optional) & “Aggregator“ (defaults to Count).

 

Below table lists options available for Primary and Secondary Group By:

Field

Available in Primary Group By

Available in Secondary Group By

Field

Available in Primary Group By

Available in Secondary Group By

Project

Key

Folder

Case Owner

Case Status

Priority

Case Type

Step Type

Component

Release

Tag

Creation Date

Automation Status

Automation Owner

Requirement

Set

(Available only if Case selection criteria is Set)

(Available only if Case selection criteria is Set)

Cycle

(Available only if Case selection criteria is Cycle)

(Available only if Case selection criteria is Cycle)

Below table lists options available for Aggregator:

Aggregator

Explanation

Aggregator

Explanation

Count

Shows the number of Cases in the grouping bucket

Presence

Shows if there is at least one Case in the grouping bucket

Effort

Shows the total of Estimated Effort for all the Cases in the grouping bucket

Examples

Cases created by Users per Quarter

This report can help in understanding the productivity of the Users. In the report input below has been selected:

  • Since no Case has been selected, the report will consider all Cases present in the Project

  • Primary grouping is done on Case Owner

  • Secondary grouping is done on Creation Date with Time period as Quarter. Date fields can be grouped by Day, Week, Month, Quarter and Year.

  • Aggregator is Count.

 

The report shows for each User number of cases created in different quarters since the start of the Project.

 

Cases in Smoke Sets by Priority

This report can help in understanding if there are lower Priority cases in Sets which need to be removed. In the report input below has been selected:

  • Smoke Sets have been selected.

  • Primary grouping is done on Set.

  • Secondary grouping is done on Priority.

  • Aggregator is Count.

 

The Report shows that AT-TS-52 Set contains Cases with Low and Not Assigned Priority. These can be reviewed to make sure Smoke Sets only contain important / relevant Cases.

 

Estimated effort for Cases in Regression Cycle by Type and Priority

This report can help in understanding the effort required to execute all the Critical cases.

  • Regression Cycle has been selected.

  • Primary grouping is done on Type.

  • Secondary grouping is done on Priority.

  • Aggregator is Effort.

 

The report is showing that by end of the first day of Regression, you will get fair idea of the build quality, since execution of all Critical cases should be completed.

 

Coverage matrix of Requirements and Cases

This report can help in understanding the coverage between the Requirement and Cases.

  • Requirement has been selected.

  • Primary grouping is done on Case Key.

  • Secondary grouping is done on Requirement.

  • Aggregator is Presence.

 

The report is showing how Cases and Requirements are linked. There are requirements which are not covered by any Case.