Forum Discussion
MisterB
2 years agoChampion Level 3
The Version and/or Iteration fields in the Test Player might help. You could use those to specify for which release you are testing. You'd first execute a test for Release 1.0, then click "Start a new test execution", change the release value, and execute that test. The test cycle also has the same fields but am not sure if that's what you're looking for in your scenario.
- AlexKuch2 years agoOccasional Contributor
Thanks for the info. However, Test Plans don't appear to have any concept of "release version" so both Test Plans still show the same status versus Test Plan Release 1.0 showing status for Release 1.0 and Test Plan Release 1.1 showing status for Release 1.1.
Is there a way to associate a Test Plan with a "release version"?
Related Content
Recent Discussions
- 6 days agoBob_C
- 7 days agotkulangara