Our documentation site has been updated to AIO Tests Knowledge Base
Project Metrics Report
The health of testing of a project, can be determined by looking at our Project Metrics Report. This report tracks progress and gives a brief overview of the project which you would like to go through before going into any details.
It also gives information (of past 90 days) of the top Cases and top Contributors working in the project.
Generating Project Metrics Report
Click on the right chevron, next to the project metrics report, and you shall see the Metrics Report.
The report output is shown above and each section is explained in detail next.
Project Overview
This gives you a concise look of project with the number of Cases, Sets, Cycles, and much more useful data. It is the data collected from the entire life span of the project.
The overview given above is explained below:
Case count – is the total number of Cases (including Draft cases) in the project
Set count – is the total number of Sets in the project
Cycle count – is the total number of Cycles in the project
Runs – is the total Runs / executions done on all cases
Defect count – is the total Defects discovered in all Runs
Automated Cases – gives the count of number of cases that have been automated
Contributors – is the total number of users, those who are case owners and those who have executed cases
Space Consumed – is the total Space occupied by the attachments of the project
If any Case/ Set/ Cycle/ Defect/ Contributor is added or removed from the project, it will be reflected in above numbers.
Activity Overview
It provides an overview of the activities done in past 90 days. The below screenshot shows that in 90 days, 43 Cases were created, 13 were updated, 9 were executed and 1 case was automated. With this, 2 defects were also logged.
Top Contributors (90 days)
It lists name of top contributors in the project, based on the Cases Created and Cases Executed, for last 90 days. The first row in the below screenshot can be read as- “AIO Documentation (user)” created 30 cases, executed 9 cases and automated 1 case (this is calculated via Automation Status and Automation Owner fields at the case level).
Top Cases (90 days)
This section shows a grid of top 50 cases (in descending order) of the project. The Cases (along with their priority and type) shown are selected from entire published case set of a project. Two very important fields in the grid are:
Used count- This count shows in how many cycles, is the particular case used.
Defects Discovered- This count shows the defects associated with the case, across all the cycles, where the particular case has been used.
Order of cases is determined by giving equal weightage (50%) to both counts- Used Count and Defect Count. The weighted average of each case is calculated by:
(Used Count of particular case/ total Used Counts) * 0.5 + (Defect Count of particular case/total Defect Count) * 0.5
The below screenshot shows project metrics report of our ATM Example. For e.g., case ADP-TC-3 is used in 3 cycles and has 1 defect associated with it. Similarly Case ADP-TC-1 is used across 4 cycles and has 0 defects associated with it.