How and When to Perform Regression Testing?
by Nataliia Vasylyna | October 1, 2013 10:00 am
It is well known that regression testing is an efficient phase of QA activities[1]. If it is performed poorly, all the preceding testing works become of no value.
That is why a software testing company advises to plan and elaborate test-cases for this type of testing thoroughly.
Regression testing is to be executed many times during a development and testing process.
It is Recommended to Perform Regression Testing Every Time When:
- new functions or/and features are added to the application;
- earlier discovered software bugs are fixed.
The aim of regression testing is to detect errors that are caused by the recent changes in the system. It is important to find and fix them as soon as possible and make sure that the software operates according to the requirements.
The First Priority of Regression Testing Should Be:
- functions with high risk;
- functions that are most often used.
When these two categories are checked one may test the rest of functionalities and paths of the application.
Regression testing is often automated. It is wise to automate checking of the code of high risk areas and the code that may be damaged by errors corrections. If regression tests are automated web site testing, desktop testing or mobile application testing requires less time, costs and efforts.
Learn more from QATestLab
Related Posts:
- QA activities: https://blog.qatestlab.com/2011/12/28/planning-of-quality-assurance-activities/
- Five Steps of Regression Testing: https://blog.qatestlab.com/2016/08/26/regression-testing-steps/
- 3 Reasons to Conduct Regression Testing: https://blog.qatestlab.com/2016/04/01/conduct-regression-testing/
- What Conclusions to Draw From Regression Tests Outcomes?: https://blog.qatestlab.com/2013/10/03/what-conclusions-should-be-drawn-from-regression-testing-outcomes/
Source URL: https://blog.qatestlab.com/2013/10/01/how-and-when-to-perform-regression-testing/