Case Usage Report
The Case Usage Report allows users to view case usage for the specified input criteria. With the help of this report, you can find out cases that have never been added to any cycle or have never been executed or that have a specific number of executions.
If a case has been added to a cycle, it is considered a single use of the case. On the other hand, if a case has been added to multiple cycles, the case will be considered to have multiple usages.
If a single or multiple runs of the same case have been created/updated in a single cycle, the case is still considered to have a single usage.
In this documentation, you will understand:
Steps to Generate Case Usage Report
Steps to Generate Case Usage Report
Step 1: To generate the Case Usage Report, simply click on the Chevron option for Case Usage.
Step 2: Once you click on the Chevron icon, the Case Usage Report modal window will appear on the screen. Fill in the fields with your desired details.
Users can provide a threshold for case usage in the Usage Threshold field. Cases that have usage at or below this threshold will be considered for the report. For instance, if you enter 1 into the Usage Threshold field, the report will only show cases that have been added to a cycle only 1 or 0 times.
If users tick the Include Cycles only from Current Project checkbox, only the cycles from the current project will be considered for the report. By default, this option will be turned on.
If users tick the Treat case versions separately checkbox, the report will list all the usage of each version of the case separately.
Users can narrow down the cases with the help of filters (Funnel icon). If you don’t have a specific field to filter by, you can add it by clicking on the Inverted Triangle icon.
Step 3: Finally, click on the Generate button.
Once you click on the Generate button, the output will be displayed on the screen.
Case Usage Report- Overview
Here’s a detailed explanation of the output of this report.
Case Usage Pareto Chart: On this chart, users can view how test cases are distributed across cycles, showing which ones are executed most often and which remain rarely or never executed.
Case Usage Cycle-Defect Scatter: On this chart, users can view the relationship between test case usage and defect detection, helping identify high-value cases and low-effectiveness ones.
Case Usage Grid: On this grid, users can view detailed case information, including cycle count and defect count, making it easy to spot unexecuted or low-execution cases.
Key: The unique identifier of the test case.
Case Version: Version number of the test case.
Title: The name/description of the test case.
Status: Current workflow status of the test case
Priority: Importance level of the test case.
Type: The type/category of the test case.
Cycle Count: Number of unique cycles in which the case has been used.
Defect Count: Number of unique defects associated with the case.
For further queries and suggestions, feel free to reach out to our customer support via help@aiotests.com.