Regression Testing.
![]()
Hi,
We're looking to start using RQM version 4.0 pretty soon.
I was wondering how people manage regression testing.
My thoughts on it were that we have a regression test plan which simply links test cases that are used in our project test plans (I'm advocating re-using the test-cases by creating test plans which refer to our new projects due to the nature of our work - a few applications with large and lengthy maintenance cycles)
Someone else is advocating changing a category field in the test case which would be 'regression'. I'm a bit confused by this as it would surely mean changing the test case (as regression tests are only identified after a phased test cycle).
My personal view is that the usefulness of the RQM is the dynamic linking of test cases to test plans (a danger if not managed correctly -agreed). So if a test case from a project is deemed useful as a regression test then surely just link it under a regression test plan.
I was just wondering how other people do regression testing using the tool as I just don't understand the advantage of changing a category field.
Many thanks for your time.
Dan.
|
Accepted answer
2 other answers
![]()
Dan,
I understand the point you mentioned. I agree with you, casting a Test case to Regression would be confusing for it's reusability. I think what David mentioned above is the right approach. Even if you still consider a separate Test plan for regression. You then don't need any thing else do to. All testcases added under it are for regression. However if regression testing if part of the overall testing effort for a release I would suggest to use what David has mentioned above. identified the Test phase when regression testing to be done. Generate TCER for Regression test phase, only for the test cases which needs to be regress tested. |
![]() Hi You could also make use of the test type. In our project, we have added custom values like Functional, GUI, Load, Sanity, Regression, etc to the test types. Best Regards Rajat |
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.