Regression testing is probably the most common interview question that any candidate face during their functional testing interview. Here in this blog, we will discuss in details about it. So, let’s begin
What is Regression Testing?
Re-executing the old testcases across multiple releases or builds to make sure that any changes that is addition, deletion or modification of new features or even bug fixes has not impacted the existing functionality of the application is known as Regression Testing
Why do we go for this type of testing?
To make sure the changes that is addition, deletion or modification of new features has not affected the existing functionalities.
When do we go for this type of testing?
Whenever some code changes are done by developers to add new features or even to fix existing bugs, we go for this type of testing.
Types of Regression Testing?
- Unit Regression Testing:
Testing only the changed features. Since there is no Impact Area
- Regional Regression Testing:
Testing Changed features + Impact Area. Impact Area is identified with the help of Impact Analysis. This are done by ->
Test Engineers– Based on their Product knowledge
Developers-> Based on their coding knowledge
Customers-> Based on their business expertise
- Full Regression Testing:
Test the changes + Test complete old features. Full RT is done in cases like Life critical or Machine critical application testing or when the Impact Area is so huge that in the new release most of the features needs to be changed.
What is the Difference between RT and Re-Testing?
Re-Testing–> Bug -–>Fix—>Test only that bug (No Impact Area)
RT–> Bug—Fix—>Test that Bug + Impact Area
So that’s it for this blog. I hope you find this blog informative and useful. For all the latest blog post updates please follow our Facebook and Instagram page. To know more about other stuff in Software engineering like Bug Lifecycle and its different stages please check our earlier blogs.