Software Testing is a very broad field, and there are possibilities and opportunities that exist wherever you turn. I find this quite exciting as Software Testers are in the forefront of creating a safe and secure world that’s ubiquitous with software. There are many aspects to learn to master in it, so one got to focus on some key aspects, some evergreen, and some upcoming. Let’s look at one of the most important topics (as perceived by practitioners), which is Regression Testing. In this blog, let’s look at regression testing meaning and its purpose. In the coming days, I am going to focus on regression testing and expand upon some important considerations related to it. Let’s get started!
Whenever someone thinks of the word ‘Regression Testing’, the picture that comes to their mind instantly is ‘repeating a set of pre-written test cases to make sure that they pass after there’s a change in the source code for a fix’, or ‘using running those automation scripts to determine PASS or FAIL so that we could spin up some metrics to gauge the quality of product, to ascertain if more testing is needed or not’.
Unfortunately, both of the above are very skewed-up understandings of what Regression Testing is. Let’s try to look at what Regression Testing is, as is.
Regression Testing is testing of software fixes to examine the thoroughness of those fixes.
Examination includes both verification and validation. Regression testing is a human effort, assisted by automation. Thoroughness is about examining whether the fixes resolve the issues for which they are made as well they don’t unintendedly introduce more issues in the areas of fixes as well in other areas.
In the subsequent blogs, we will look at some of the most common misconceptions and wrong notions about Regression Testing.
Feel free to get in touch with me to discuss Regression Testing Meaning and its purpose.