Maintaining an Effective Regression test suite, how?

(Kim) #1

If we take the pre-condition here we all understand what regression testing is.

Questions:

When does a test case/suite effectiveness diminish?

Bugs in the prior release would you manually execute some regression testing around this for the next release or would you include them into the current suite. - Is inclusion based on the bug priority

What steps do you apply to maintain optimisation? Does anyone use a tool to track features and corresponding tests (or is this just a matter of tags)?

Really looking for a way to maintain good housekeeping processes within testing :slight_smile:

(Joop) #2

Hello Kim,
In every regression test I assume that the previous release was without bugs. So of there were bugsin the previous release, I report them again.
In the organization where I work, we have divided the regression test in separate parts. One colleague does the financial part, another one does the webpage and I do the output.
To check the output, I have automated the input with a robotic tool so I know for sure that the input is exactly the same.
The output I check with a simple tool named Nuance.

Joop

(Kim) #3

thanks for the insight Joop. will look at that tool :slight_smile:

(Jason) #4

A set of regression tests should remain effective and relevant as long as you update it with new features (after first detailed testing), include re-tests for bugs found in previous text cycles (especially critical or revenue affecting bugs) and remove tests that are no longer necessary. That last point especially true for manual testing where you’re not necessarily going to have time to focus on less important (or unused) functionality.

(Kim) #5

thanks Jason its good to know I am on the right track :slight_smile:

(Mary) #6

Make sure your current release test cases are to the point and reusable. In general, an entire system isn’t redesigned in every release. Using updated test cases from the previous release cycle is an effective way to maintain a regression suite. If changes are made, update the test case(s) to match the updated functionality.

Another good resource is the previous release’s User/Business Acceptance Tests. These are generally a high level set of end to end test cases that cover what the users consider to be the important system functionality. Just make sure the pertinent steps are updated that reference the current release changes.

(Kim) #7

thanks Mary good points