Retesting - Retesting is a type of testing where we retest the updated bugs in time of testing the application after resolving bugs by developers.
We raise the bug when we find it while testing the application. Then we assign the bug to a developer and then resolves it. After fixing, the bug is re-assign to us(tester) for the retesting.
Re-testing is done on the basis of the bug fixes. Priority of re-testing is high so it is done before regression testing. It has to be carried out prior to regression testing. The purpose of retesting is that the original fault has been corrected and done for all failed test cases. The test cases are obtained after testing.
It is already planned to test after bug founded. We prepare with the same cases after new build update. And we need to ensure that this is executed in the same way as it was done the first time with the same environment, data and inputs.
We don't need to prepare separate test cases for the retesting as mentioned above it would be done with the failed cases. Also, we don’t need to recheck the past cases as it is covered in regression testing.
The test cases related to the defect are executed again to confirm that the defect has indeed been fixed.
After retesting we ensure that reported bugs are corrected.
Regression Testing - Regression testing is a type of testing where we test the functionality or fixed bug of existing module of software or application and that must not affect the other functionality or area of the software.
We need to do the regression testing whenever test new changes or retest the updated bugs by the developer. So the main purpose of it is that the new changes in code should not affect to other existing functionalities or module of software.
According to project and availability of resources, regression testing and retesting are done parallelly. The entire module is required to be re-tested to ensure the quality of the module that is regression testing. Regression testing is done for passed test cases to get the unexpected side effects of the same.
We need to do the regression testing whenever there is a modification in the code based on the change in requirements. A new feature is added to the software.
We check the defects are fixed in the entire application. And the major functionalities issues are fixed in the application.
Regression testing also checks for unexpected side-effects.
We can do the regression testing as per the below different situations:
- When the application is ready to go live we need to check the whole application with all the test cases and ensure that the software is now bug-free and can move to live.
- We can choose a specific part of the test cases which need to be executed in every regression cycle and do only for those.
- Based on the business, timelines, feature criticality, choose the specific test cases and execute only those.
- Select a sub-part of test cases based on frequent defects, visible functionality, integration test cases, a sample of successful and failed test cases and then execute only those sub-part.
Hope you find this info.regarding Retesting And Regression Testing helpful and need more QA assistance then contact us now. Feel free to give your reviews on it.