Regression vs Retesting
Generally, regression testing is performed in order to assure that current functionality operates appropriately, and all code modifications did not break the work of other systems.
Executing software product testing, the specialists also execute retesting to ensure that the certain defect was fixed and all functionality works correctly.
What are the differences between regression checking and retesting?
- Error verification is not included into regression testing, comparing to retesting.
- Regression testing cannot be conducted simultaneously with rechecking which has higher priority and is performed before regression testing.
- Automation is applied only to regression tests, retests are not automated.
- Absolutely all tests are rechecked under regression testing, while under retesting - only the failed ones.
- Checking the unforeseen indirect factors is the goal of regression testing. Retesting is fulfilled to confirm that original features operate as it was expected.
- Regression checking is executed in the case when new system features were added or the modifications or improvements of the code itself were performed. Retesting is conducted, using the same data and in the same environment as before but on the new build already.
- The test cases for regression testing may be created on the basis of project specification or other documentation and also on the basis of the ready bug reports. Retesting test cases may be available only after completing the test process itself.