Regression testing is the process of testing changes to computer programs to make sure that the
older programming still works with the new changes. Regression testing is a normal part of the
program development process and, in larger companies, is done by code testing specialists. Test
department coders develop code test scenarios and exercises that will test new units of code after
they have been written. These test cases form what becomes the test bucket. Before a new
version of a software product is released, the old test cases are run against the new version to
make sure that all the old capabilities still work. The reason they might not work is because
changing or adding new code to a program can easily introduce errors into code that is not intended
to be changed.
||Getting started with regression testing
|To explore how regression testing is used in the enterprise, here are some additional resources
for learning about software quality assurance tools:
testing fundamentals - Regression testing: Regression testing ensures that little changes don't
break software. Good regression testers need to know what they're looking for, and this guide
testing is more than retesting: Regression testing is a necessary component to any software
development lifecycle. Expert Mike Kelly explains the motivations for conducting regression
to conduct regression tests: If regression testing is part of your test plan, here is some
advice you should follow. Expert Mike Kelly explains how to properly conduct such testing.
This was last updated in February 2007
Register now to receive SearchSoftwareQuality.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy