updating test plan with new version of test cases
editing of different Testcase-Versions
I have a solution of your problem:
Create to every TestSpec only one TestPlan = 1:1 relation
Make a Testspec1 and create only one built = built1 and only one TestPlan = TestPlan1 for this Testspec1.
When you have a new Software-Built to test, then make a copy of your TestSpec1 = TestSpec2, create a Built2 and a TestPlan2.....and so on.
By this way you can edit different Testcase-versions in different TestPlans without TC-versions-problems.
By this way you may have in every builts a different Testcase-Set.
But you have the following disadvantage:
Your testprojekt-Database is growing much more, because every Software-Built has its own independent TestSpec.
Hint:
The name of the TestSpec contains the name of the SW-Built.
The name of the TestPlan contains the name of the SW-Built.
Advantage of this procedure (workaround):
You never have problems with Testcase-Versions in different TestPlans.
You can edit the testcases in every SW-built without any dependency.
Its very simple to understand the 1:1 relation between Testspec and TestPlan, because this is a well arranged Testenvironment.
Let me know your opinion about my Testlink-strategie.
Create to every TestSpec only one TestPlan = 1:1 relation
Make a Testspec1 and create only one built = built1 and only one TestPlan = TestPlan1 for this Testspec1.
When you have a new Software-Built to test, then make a copy of your TestSpec1 = TestSpec2, create a Built2 and a TestPlan2.....and so on.
By this way you can edit different Testcase-versions in different TestPlans without TC-versions-problems.
By this way you may have in every builts a different Testcase-Set.
But you have the following disadvantage:
Your testprojekt-Database is growing much more, because every Software-Built has its own independent TestSpec.
Hint:
The name of the TestSpec contains the name of the SW-Built.
The name of the TestPlan contains the name of the SW-Built.
Advantage of this procedure (workaround):
You never have problems with Testcase-Versions in different TestPlans.
You can edit the testcases in every SW-built without any dependency.
Its very simple to understand the 1:1 relation between Testspec and TestPlan, because this is a well arranged Testenvironment.
Let me know your opinion about my Testlink-strategie.
Thanks for the suggestion. However, our organization designs one software product and in between major releases we release maintenance as well as new features. Our test cases are reused continously and always will be. In the situation I mentioned, I just left it as is, and noted which test cases were inaccurate, next release they will be accurate. I will never get in this situation now since i enabled the editing of locked test cases. Anyone else out there use testlink to test a single product and reuse data?