proper process?

[davej409]

I have been using Testlink for a long while now but one thing that always bothered me is if I realize that I am missing a test case and add it to the test plan, it skews the results of all the previous builds. I realize that the percentage calculations are accurate, the test was not run against the previous builds because it was just added to the test plan...but I can't go back to each build to preserve the percentages every time I add a test case and I don't think making a new test plan everytime I add a new test case is the answer either. Open/Closed and Active/Inactive builds don't seem to help.

So, is there a proper way to add test cases in the middle of a release without screwing all of the results of prior builds? I should mention I am on v1.8.3. I took a look at the release notes for v1.8.4 and v1.8.5 and didn't see anything that seemed related so I didn't want to start upgrading until I got some feedback. Plus, I am not entirely sure if its a software issue or (my) user error in the workflow process.

Any help is much appreciated...

Thanks,
-Dave Johnson

[fman]

you need to upgrade to 1.9

[JohnE]

But 1.9 is not released so should not be used for "real" testing.

[davej409]

Thank you both, understood. I can't wait for the GA version. I need to take a look at a release candidate but have been so busy, I haven;t had a chance. Thanks for a great product.

[Amaradana]

I have been using Testlink for a long while now but one thing that always bothered me is if I realize that I am missing a test case and add it to the test plan, it skews the results of all the previous builds. I realize that the percentage calculations are accurate, the test was not run against the previous builds because it was just added to the test plan...but I can't go back to each build to preserve the percentages every time I add a test case and I don't think making a new test plan everytime I add a new test case is the answer either. Open/Closed and Active/Inactive builds don't seem to help.

So, is there a proper way to add test cases in the middle of a release without screwing all of the results of prior builds? I should mention I am on v1.8.3. I took a look at the release notes for v1.8.4 and v1.8.5 and didn't see anything that seemed related so I didn't want to start upgrading until I got some feedback. Plus, I am not entirely sure if its a software issue or (my) user error in the workflow process.

Any help is much appreciated...

Thanks,
-Dave Johnson

Well can i tell you a work around with 1.8.5, You can always generate the query metrics report for time being. When 1.9 GA is released you can migrate