| || |
When do progressive test cases become regression test cases?
For the sake of this question:
progressive: test cases which verify new/updated features
regression: test cases which verify features that have not been touched
Can you please describe your complete process surrounding these 2 different types of test cases, and even how you organize them within your chosen test case management tool?
It seems logical to me that when some aspects of the SUT have changed, we examine the requirements to generate progressive test cases which address those updates. We store those progressive test cases in some way, and we attach them to our test plan for execution.
At the same time... it seems logical that we should also test important features of the software which are not expected to have changed just to ensure that they have not changed. Presumably these regression test cases already existed as a result of the v1.0+ rounds of testing and were stored in some kind of regression pool taxonomy (perhaps organized by business function or by application if there are multiple). We also select & attach some (or all) of these to our test execution plan.
My questions are:
1. Do you attach both progressive & regression cases in the same execution plan or do you have separate plans for each?
2. At what point do your progressive test cases get promoted to regression test cases?
3. What process do you use to select which progressive test cases get promoted to regression test cases and which ones don't?
4. Do you MOVE the promoted test case into the regression pool, or COPY it (resulting in a duplicate within your test case management system)?
5. What do you do with progressive test cases that didn't get promoted into regression cases?
6. Do you archive your entire collection of executed test cases (progressive + regression) that were executed for the test cycle?
Hope that makes sense.
Reply to this is given in another post. Still pasting my reply again here...
Based on how you have defined "progressive", these are all the basic test cases in your current library not marked for regression.
Hence.... for your questions:
1. do you attach both progressive & regression cases in the same execution plan?
2. at what point do your progressive test cases get promoted to regression test cases?
It depends on your regression approach. Ideally, it is for each primary build.
3. what process do you use to select which progressive test cases get promoted to regression test cases?
You need to do an impact analysis on the fixes / features coming in the build. Based on the same, you can decide on which test cases can be marked as regression.
4. do you MOVE the test case to the regression pool, or COPY it (resulting in a duplicate within the test case management system).
From a library, you will always copy to a Test Plan. If you are using a tool, it will anyways never allow you to MOVE test cases to a plan.
5. what do you do with progressive test cases that didn't become regression cases?
Nothing. These remain in your library for a future consideration.
6. do you archive your entire collection of test cases (progressive + regression) that were executed for the test cycle?
Progressions and regression are attached in same execution plan.