Forum Discussion
Part 1
Hi JuanCarlos, AndreaC,
This is an interesting scenario. What you are trying to do is report in the direction of Test Case > Test Execution, whereas I think Scale is more suited to reporting based on Test Execution as the starting point. But I believe it's still possible to report in the way you want π
In my tests, after replicating your scenario, I went to the Configuration menu and added two Iterations, e.g. v1, v2. I then assigned v1 to all tests in Cycle One (10 pass, 10 fail), and assigned v2 to 10 tests that passed in Cycle 2 (leaving the 10 not executed without an iteration).
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).
This worked for me - I got 20 results in total, showing the latest result for all executions in v1 & v2. You may still encounter issues because the report is based on all executions in those cycles, so another option is to swap Test Cycles filter criteria and instead use Test Case > Folder criteria (making sure that your test cases are structured in folders how you would like them reported).
I think there is another way to do this - possibly cleaner - and will report back on that in Part 2 π.
Let me know if this works for you?
Thank you very much for your help. After reviewing both cases, the first one would be the best fit for our way of working. However, after following your suggestion (assigning iteration 1 to all test cases from the first test cycle, whether they passed or failed, and iteration 2 only to those executed in the second test cycle), when applying the filter as per your instructions, it displays all the test cases executed in iteration 1 plus those executed in iteration 2.