...
The Total Platforms and Total Test Cases columns in report displays the respective association with the test suite.
...
Filter Report:
Click on the Filter icon on the individual chart to generate the report as per requirement by applying multiple filters.
...
NONE: If the test case is not executed under any build, then the execution status is shown under the None column.
Last Executed Build: Last Executed Build column shows the build name the test case was executed last.
...
Filter Report:
Click on the Filter icon on the individual chart to generate the report as per requirement by applying multiple filters.
Project (mandatory)
Release (mandatory)
Cycle (mandatory) Report will work on cycle level (Single cycle only), this will be mandatory filter.
Build: The selected build details will be displayed in the report if test cases are executed on that build. If a build is not selected, details of all the builds with execution will be displayed. Archived build will not be displayed.
...
.
...
Planned vs Actual Execution
Planned vs Actual Execution analysis gadget under the Test Execution Summary report helps QA managers understand the current and expected execution rate to meet the release timelines. The report displays a Line Chart which that indicates the execution progress during particular sprint/period. It helps leads/managers review the current progress of test execution against the planned test execution and make decisions regarding resource allocation/task distribution to achieve the target.
The test run scope is defined through the selection of Project, Releases and Cycles. The list of test suites to be considered for planning is defined by applying necessary filters like Folders Path/Folder Name, Platform and Test Suite Key. This gives the total count of test execution runs planned for the selected scope.
The report can also be generated to have a granular view of the execution progress of individual assignees.
Planned Execution: Number of test executions planned during a particular sprint/period. It is calculated by applying the formula: Total Test Executions Planned/Number of Days. The chart shows cumulative count of the planned test executions.
Actual Execution: Number of test executions actually carried out during a particular sprint/period. The chart shows cumulative count of the actual test executions as per selected execution statuses.
For example,
A sprint is planned for 10 working days. There are 5 test suites with 50 test execution runs to be executed during the sprint.
Planned Executions will be calculated as 50/10 = 5 per day planned executions (i.e., 5 executions should be performed every day to complete the testing on time.) The chart will be plotted on the cumulative executions planned daily.
Actual Executions chart will be plotted based on the cumulative executions performed daily.
Current Average and Required Average Test Executions
Current Average of test executions is the actual average executions carried out in current time period.
Required Average of test executions is the rate at which the test executions should be performed to achieve the sprint target.
The following formulas are applied to get the values:
Current Average Test Executions = Total Actual / Completed Time Period
Required Average Test Executions = ( Total Planned - Total Actual ) / Remaining Time Period
Note: Required Average rate will be generated only if future date is applied in the filter.
If the Show Test Suite with Details option is selected in filter, the chart displays the actual progress of each test suite in the scope. The legend shows Test Suite Key and color. On hovering Test Suite Key, it shows Test Suite Summary. You can also disable test suite key to hide its data on the chart.
...
If you hover over an execution in the chart, it shows further details regarding that execution.
...
Filter Report:
Click on the Filter icon on the individual chart to generate the report as per requirement by applying multiple filters.
View By: Select from the options Day, Week and Month. For Daily report, you get an option to skip particular days from the calculation of duration. For example, 100 test execution runs to be completed in 10 days from 1st October to 15th October (excluding Saturday & Sunday).
Start Date and End Date: Start Date of Execution and End Date of Execution. The duration of sprint for which the Planned and Actual Test Execution Run will be calculated.
Project: Only one project can be selected.
Release: Release values populated in accordance with the project selection above.
Cycle: Cycle values populated in accordance with the release(s) selection above.
Execution Status for Executed Case: Select Execution Statues that should be considered as executed. For example, test executions with status “Passed”, “Failed” and “Not Applicable” are considered as executed. Rest of the execution statuses are not considered as executed. This filter is only applicable for actual executions.
Folder: Browse and select the test suite folder to consider the test suites under that folder for planning. If a parent folder is selected, then all the sub-folders under that parent will also be considered.
Assignee: Select a test suite assignee to have a granular view of execution progress of that individual assignee.
Platform: Select the platform(s) to consider test executions on that particular platforms for planning.
Test Suite Entity Key: Enter a single test suite key or comma separated test suite keys to consider those test suites for planning.
Show Test Suite with Details: Select the check box to view the actual progress for each test suite in the scope.
...
Export Report
To export the report, click on the cog icon for the report and select Export Raw Data.
...