Regression Test Plan
Posted: Tue Mar 02, 2010 8:48 pm
We have a certain subset of test cases that have the keyword 'Regression'.
These high priority tests are ran after each code lock.
The assigned user for each test case is the same among each release.
I am seeking some advice on how best to utilize testlink for our needs.
Option 1: Create a "Regression Test Plan" that consists of all tests w/ keyword = Regression. Then assign tests to their appropriate tester. Then, for each code lock for a release, we create a new build.
Benefits:
Benefits:
These high priority tests are ran after each code lock.
The assigned user for each test case is the same among each release.
I am seeking some advice on how best to utilize testlink for our needs.
Option 1: Create a "Regression Test Plan" that consists of all tests w/ keyword = Regression. Then assign tests to their appropriate tester. Then, for each code lock for a release, we create a new build.
Benefits:
- Test assignments are maintained.
- Reporting is a mess and shows overall results for all builds in the plan. We had hoped it would have option for reporting only on the most recent build or report based on the build active/open status.
Benefits:
- Reporting works as desired by only reporting on the current regression execution because we only have the one build defined.
- We have to reassign tests each time which is just tedious and time consuming in determining who has what.
- If there is a way to maintain test case assignment when you create a plan from an existing plan.
- Any future plan for this ability?
- Any other suggestions on how this could be set up?