Hi.
I agree with the structured approach that mohana suggests - it's how I also work, except instead of creating a new sprint test cycle, I clone the previous sprint test cycle (which clones the test cycle and all test cases, and sets the execution status as Not Executed). From there it's a simple case of removing test cases that you don't want to re-execute in that test cycle.
Cheers, Andy
Thank you for your responses. The problem with cloning or creating a new test cycle is that I would lose the test execution history. I like easily seeing the previous test runs at the bottom (screenshot attached). I can explain a little better how we're using zephyr on my team (Maybe there's a better way). We use Zephyr for our regression testing. We have test cycles for each large feature and test cases within those cycles related to that feature. Whenever we have a big release, we like to run full regression and execute every test case we possibly can. This means we are executing multiple test cycles so it would be nice to easily start a new test execution for all of our test cycles. This would preserve the history of the previous regression testing so we can be better informed (Is this test case failing because of a new issue, or has it been broken for a while).
