Re-testing vs. Regression Testing
Difference between Regression and Re-testing are most haunting software testing question asked in any interview by interviewer and we normally get confused between Regression and Retesting
We as tester do Retesting and Regression testing all our life, Whether we reach on the top of ladder of this profession or has just started the profession.
Software testing is a kind of fun and if you are not enjoying the software testing, It means you are not following the right method of testing.
Since we people are linked with the testing of software, we all would be pretty familiar with the word Regression and Retesting. Since both sound similar and comes in to action just after a bug-fix, so most of the time we people get stuck to the fundamental difference between Retesting and Regression.
Here i am going to note down
Difference between Regression and Retesting
1-Retesting is done to make sure that bug is fixed and failed functionality is working fine or not, This is kind of verification method followed in testing field for the fixed bugs. Whereas, Regression is re-execution of the test cases for unchanged part to see that unchanged functionality is working fine are not.
2- Retesting is a planned testing while Regression is known as generic testing.
3- Retesting is only done for failed Test cases while Regression is done for passed test cases.
4- We should always keep this in mind, Re-testing has higher priority than the regression testing. But in bigger projects Retesting and Regression is done in parallel effort.But never forget importance of both in the success of the project.
Let me explain my things with an example.
For eg: in an application we need to manage college accounts department, college hostel department and college academic department. There are three modules. A bug was found in hostel module. So, it needs to be retested. And since accounts module depends on hostel module, so regression testing would be done on hostel module also.
Courtesy: Amrit Kaur