search

dwyl / technical-glossary

📝 A collaborative technical glossary for key words and terms to help anyone learn and understand concepts and prepare for a career as a creative technologist! 😕 > 🤔 > 💡 > 😊 🎉 🚀
GNU General Public License v2.0
26 stars 5 forks source link

New words: Regression testing #21

Closed Cleop closed 5 years ago

Cleop commented 5 years ago

Relates to: https://github.com/learnTrack/Q-A/issues/68

Cleop commented 5 years ago

Regression Testing - the re-running of existing tests to ensure that new changes/fixes have not broken any existing functionality.

From wiki:

Regression testing (rarely non-regression testing) is re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change. If not, that would be called a regression. Changes that may require regression testing include bug fixes, software enhancements, configuration changes, and even substitution of electronic components. As regression test suites tend to grow with each found defect, test automation is frequently involved.

when a bug is located and fixed, to record a test that exposes the bug and re-run that test regularly after subsequent changes to the program

Regression testing is performed when changes are made to the existing functionality of the software or if there is a bug fix in the software. Regression testing can be achieved through multiple approaches, if a test all approach is followed, it provides certainty that the changes made to the software have not affected the existing functionalities, which are unaltered.

From https://www.guru99.com/regression-testing.html:

Regression Testing is defined as a type of software testing to confirm that a recent program or code change has not adversely affected existing features.

Regression Testing is nothing but a full or partial selection of already executed test cases which are re-executed to ensure existing functionalities work fine.

This testing is done to make sure that new code changes should not have side effects on the existing functionalities. It ensures that the old code still works once the new code changes are done.

From https://www.softwaretestingmaterial.com/regression-testing/:

regression testing by re-executing the tests against the modified application to evaluate whether the modified code breaks anything which was working earlier. Anytime we do modify an application, we should do regression testing

From http://softwaretestingfundamentals.com/regression-testing/:

regression testing is conducted to make sure that fixing one thing has not broken another thing.

During regression testing, new test cases are not created but previously created test cases are re-executed.