Forum Discussion
I might be mistaken and have missed a feature but I don't think test plans are designed to work in that way. The status of a test plan is a text description as to the readiness of the test plan. The status won't update automatically based on the tests executed in the test plan's test cycles. To me, the test plan is only useful for logically grouping test cycles and referencing that test plan in a report (instead of having to reference multiple test cycles).
I think you need to use test cycles. They have readiness statuses as well but they also have execution statuses that automatically update based on the execution status of that cycle's test cases. So using your example you could have 2 test cycles for each release. Or you could have 1 (as per my example) - you run it once for v1.0, then change the release/iteration of the cycle to 1.1 and then you start a new execution of the tests for v1.1 - whichever best suits your needs.
Related Content
Recent Discussions
- 12 hours agotkulangara
- 15 hours agoUrsK
- 7 days agoBob_C