Regression testing is not a phase in SDLC (at least not anymore)<\/p>\n

Regression should be happening at multiple levels across the development process.<\/p>\n

In a waterfallish setup, you’d typically have a few days where teams try to execute all ‘regression’ test cases<\/p>\n

While there are a lot of things wrong with that picture, I want to focus only on what we call ‘regression testing’<\/p>\n

In simple terms, all functionality we want to check & see if it’s still working after changes we’ve made – that’s regression.<\/p>\n

In a DevOps culture, there should be decent automation in place, at unit, integration & System integration level.<\/p>\n

All these automated tests are ALSO REGRESSION. Yes, a unit test which is important for us to ‘regress’ on is regression. I don’t know how come UI tests became synonymous with regression.<\/p>\n

So holding on to that behemoth set of test cases which are supposed to be run ‘just before release’ is not efficient<\/p>\n

And if that’s happening in your team, I wouldn’t be surprised if testing is considered a bottleneck.<\/p>\n

#RedefiningSoftwareQuality<\/strong>\u00a0✔\u00a0#Testing<\/strong> #TestAutomation<\/strong> #RegressionTesting<\/strong> #AgileTesting<\/strong><\/p>\n<\/div>