Test Execution Records are not available in a copy of a test plan
![]() If we are going to release a new major version of a product, we copy the test plan of the previous version along with all the test cases and then add the test cases for the new features. However the test execution records (in my understanding the combination of a test case with a test environment) are not copied to the new test plan, as there is a one to one relation between test execution record and test plan. We have to create new test execution records in the new test plan. This is inefficient, as the existing test execution records typically do not change, moreover, the names of the new test execution records created within the new test plan are by default identical with the names of the old test execution records (the name of the test case and the test environment are the same! ). That causes a bunch of test execution records with the same name , which can only be differentiated by their ID and test plan association (makes it difficult to pick the correct test execution record in various drop down lists). Now the question: Is there a way to make the existing test execution records available in a new test plan, which uses the same test cases as in another, older test plan. What is the reason, that a test execution record can only be associated with one test plan? The same holds true for test suite execution records Best Regards, roland |
Accepted answer
![]()
RQM 4.0.1
Could you consider not doing a copy of Test Plans and instead use TimeLines associated with a singe Test Plan? The Timeline could be structured around you releases. When the time comes to set up for the next testing cycle Test Execution Records in the Test Plan can be copied to a new Iteration from the timeline and new Execution Records could be generated for newly added test cases.
Roland Mueller selected this answer as the correct answer
|
2 other answers
![]()
This capability is being considered for 4.0.3.
See this story As a user, I can choose to copy an execution record to different plan, test case, or iteration (80168) |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
@Roland,