Regression testing: Difference between revisions

Revision as of 10:23, 29 September 2004

Revision as of 10:24, 29 September 2004

Line 7:

Therefore, in most software development situations it is considered good practice that when a bug is located and fixed, a test that exposes the bug is recorded and regularly reperformed after subsequent changes to the program. Some projects even set up automated systems to automatically re-run all regression tests at specified intervals (usually daily or weekly) and report any regressions. Or, if you are using [[make]], you could set up your makefile to automatically run the regression tests after every successful compile.

Regression testing is an integral part of the [[extreme programming]] software development methodology. ThereIn the extreme programming methodology, design documents are replaced by extensive, repeatable, and automated testing of the entire software package at every stage in the [[software development cycle]].

Regression means to step backward. When software changes are made that break stuff that used to work, it is considered to regress. Regression is the opposite of progress.