How to Generate a Summary Report for Multiple Test Cycles Without Duplicating Cases
Hello,
We are currently migrating our testing tool from TestLink to Zephyr Scale, but I've encountered a problem with generating our follow-up reports. In TestLink, we used to create reports where we displayed the results of the last version's executions along with the cumulative total of all versions tested.
Here’s the scenario:
I have a Test Plan with 20 test cases, and there are two test cycles (builds) associated with it. In the first cycle, all test cases were executed, with 10 passing and 10 failing. In the second cycle, we only had time to re-execute the 10 failed cases, which now pass.
When generating a summary report in TestLink, I could select both builds, and the graph would display that there are 20 test cases, with all of them passing (10 from the first build and 10 from the second). However, in Zephyr Scale, if I select both test cycles, the report shows 40 test cases (duplicating the test cases), which is not the result I want. I would like Zephyr Scale to behave like TestLink, showing a total of 20 test cases without duplicating the executions.
Is there a way to generate the summary report in Zephyr Scale without summing up the test cases from both test cycles?
Thank you for your help!
Hi, sorry, I missed a key part of the solution where you need to change reporting to be based on the Test Case Folder location! This means changing your report to not report by Test Cycle. This paragraph is now corrected:
From:
In my report, using the Advanced Filtering option, in Test Cycles I added the two Cycles, and in Test Execution, chose Iterations v1, and v2, and set the Results output to Last Test Execution (the default value).To:
In my report, using the Advanced Filtering option, Test Cases, I selected the Folder where the tests are stored, and in Test Execution, chose Iterations v1, and v2, and set the Results output to Last Test Execution (the default value). This solution requires you to file tests logically by folder (which hopefully is what you're already doing), but the advantage is that you can now report executions by folder (i.e. by test case), and show the latest result for those tests regardless of how many test cycles they appear in, e.g. v1, v2, v3, etc.
