Throughout my career from being a manual tester to test engineer to test architect to head of delivery, one question came up time and again: how do we do testing in agile?
Releasing frequently is essential in agile, but waiting for a gatekeeping tester to do regression tests at the end of each sprint wastes valuable time. This approach has led many teams to reject testing entirely, but there’s a better way to do it.
Are you struggling to reconcile the need for frequent releases with the demands of quality assurance? Many teams have rejected testing in Agile due to the assumption that it should happen at the end of the delivery cycle, leading to bottlenecks and compromised quality. But there is a different way to do it – one that allows you to move quickly and nimbly without sacrificing quality.
As a test professional, you may have wondered how to adapt your testing practices to fit into the Agile development process. Throughout your career, you may have encountered the same question time and time again: how do we do testing in Agile?
Fortunately, the Agile Manifesto provides 12 principles that can guide you in delivering stable software multiple times a day/week/month or whatever your cadence is. In the coming weeks, we’ll explore how to translate these principles into concrete actions your test team can take to increase quality and assure stable software delivery.