Sometimes one step forward turns into two steps back. We know that in the world of software development. Solutions originally intended to fix problems can create new and potentially more serious problems.

Enter regression testing. This discipline enables us to track issues, check the effectiveness of a solution, and detect any new issues which may have been created as a result of fixing the original problem. Reports are generated, problems are tracked, and the process continues until all of the issues are solved or a new version is developed.

The purpose of regression testing is to ensure that previously detected and fixed issues really are fixed, they do not reappear, and new issues are not introduced into the program as a result of the changes made to fix the issues.

Typically influence software performs regression testing on a daily basis. Once an issue in the defect tracking database has been fixed it is reassigned back to influence software for final resolution. influence software can either reopen the issue, if it has not been satisfactorily addressed, or close the issue if it has, indeed, been fixed.

For more involved projects lasting several months, several full regression passes may be scheduled in addition to the continuous regression testing mentioned above. Full regression passes involve re-verifying all closed issues in the defect tracking database as truly closed. A full regression pass is also typically performed at the very end of the testing effort as part of a final acceptance test.

In addition to verifying closed issues, regression testing seeks to verify that changes made to fix known defects do not cause further defects. influence software can produce a regression testing suite consisting of test cases that evaluate the stability of all modules of the software product. Quite often, automation of this regression testing suite is well worth considering.