Regression testing compares two builds or versions of the same target-of-test and identifies differences as potential defects. It thus assumes that a new version should behave like an earlier one and ensures that defects have not been introduced as a result of the changes.

Ideally, you would like all the test cases in one iteration to be used as test cases in the later iterations.  The following guidelines should be used to identify, design, and implement test cases that maximize the value of regression testing and re-use, while minimizing maintenance:

• Ensure the test case identify only the critical data elements (those needed to create / support the condition being tested)
• Ensure each test case describes or represents a unique set of inputs or sequence of events that results in a unique behavior by the target-of-test
• Eliminate redundant or equivalent test cases
• Group together test cases which have the same target-of-test initial state and state of the test data

Related Articles

• Why Thinking ‘Inside the Box’ Is Sometimes Effective for Test Automation (0)
• Using Java to Import and Manipulate Microsoft Excel (0)
• How to Regression Test a relational database (0)
• What to consider when testing databases (0)
• How to use JMeter for performance testing (0)