Regression Test Plan

Discuss test processes, standards, documentation, teams, criteria, test environments, etc.

Moderators: Amaradana, TurboPT, TL Developers

Post Reply
cjames
TestLink user
Posts: 4
Joined: Thu Feb 04, 2010 4:50 pm

Regression Test Plan

Post by cjames »

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:
  • Test assignments are maintained.
Negatives:
  • 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.
Option 2: 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, deactivate the previous plan and create a new plan for the current release.
Benefits:
  • Reporting works as desired by only reporting on the current regression execution because we only have the one build defined.
Negatives:
  • We have to reassign tests each time which is just tedious and time consuming in determining who has what.
We think Option 2 is best for our process but would like to know...
  • 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?
Thank you!!
Amaradana
Member of TestLink Community
Posts: 398
Joined: Mon Feb 16, 2009 11:19 am
Contact:

Post by Amaradana »

Hi,

My thoughts on how you can utilize and organize and the decision is up to you to choose.

Option 1 : Yes when we have one test plan for 'n' builds results are for the overall, but not for the last build. I wish we can over come this by Query metrics report.

Option 2: Yes this is a good method but for every release if we keep creating a test plan the results may be accurate. i think you can copy the test cases that are assigned for testers. for this type of situation there are some more interesting reports are made in 1.9 version, where you bring all the results together and show the results. Check our tracker for that.

Thanks,
Amaradana
Thanks,
TesterWorld
Http://amartester.blogspot.com
Post Reply