Regression testing is re-running utilitarian and non-useful tests to guarantee that recently created and tried programming despite everything performed after a change. If not, that would be known as a regression.”
In the event that you ask me what regression testing is, I’d answer something like, “It’s a sort of programming testing to ensure another change to the code didn’t break existing usefulness.”
Importance of regression testing
Regression testing is important. Tragically, now and then an organization will believe it’s doing relapse testing when really it’s simply doing retesting. Retesting is tied in with ensuring that a particular code change works as indicated by desire. Relapse testing is tied in with guaranteeing that the whole framework attempts to desire once a change has been presented. In that capacity, planning and actualizing relapse tests has a lot more extensive extent of action than retesting.
Commonly, retesting happens rapidly, at or exceptionally close to the time code is being made. Relapse tests happen further along in the SDLC when additional time is accessible to oblige the more extended period of time required to execute the testing. Truly, some retests can be very mind boggling and tedious, however not even close to the time span required to execute a complete relapse test. Keep in mind, sufficient relapse testing implies that all parts of the framework must be tried and similarly as critically, observed. Playing out a relapse test without sufficient, framework wide checking set up transforms the testing exertion into a speculating game. As we showed in the initial situation, a blunder can happen in one piece of the framework, yet be brought about by conduct in another part. Sufficient checking gives you the experiences into the framework you need so as to decide issues and main drivers.
TestingXperts 