Member-only story
Why do we conduct Regression Testing? How does it work?
Regression Cheatsheet
In this Agile world of multiple releases per month, we as SDETs need to make sure the testing is completed as soon as possible and we can push quality releases.
What is Regression Testing?
The testing which is conducted after the code update or alteration of a feature/functionality. This testing primarily focuses on that the changes made does not introduce any new defects or damages existing features.
When to perform Regression Testing?
Once the changes are completed and made available to the QA team in the lower environments we can conduct a quick testing (re-testing if its a bug fix) to evaluate the feature is working and doing what its intended to do!
Hence we can call it a subset of re-testing which basically confirms whether the application is working without any issues.
How to perform Regression Testing?
1) Determine the tests selection
We can use different ways and below are some steps:
- Understanding the feature by discussing with dev team
- Understanding the requirements