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: |
| Software
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
explains how. |
| Regression
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
tests. |
| How
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
Email Alerts
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
More News and Tutorials
-
Software consultant Nari Kannan describes how agile practices and work can be scaled appropriately for success in large organizations. Using lean thinking, reduction of waste, and appropriately organizing work and people, agile can be successfully adapted, regardless of the size of the organization.
-
Undiscovered software glitches in complex systems are common, and one of the primary drivers is the loss of mainframe knowledge of a retiring workforce. Software glitches are lurking in many large systems, particularly mainframe systems, and the COBOL programmers that understand the code best are retiring, according to Jeff Papows, author of the new book, "Glitch - The hidden impact of faulty software." Papows describes how faulty software caused a huge charge to debit card holder's account and why such mistakes are on the rise in this interview. Papows notes the three most pressing drivers for software glitches: loss of intellectual knowledge, market consolidation and the ubiquity of technology
-
Karen Johnson suggests a variety of ways that testers can gain additional skills and experience, including social networking and open source testing.
