Eliminate Regression Testing through Continuous Deployment

Most traditional teams do testing at least twice—once during development as new features are created and again during release candidate testing right before release. As a system grows, regression testing takes more and more time, making tight releases impossible—or at least risky—and adding to the burden of maintaining automated tests. Matt Heusser suggests that adopting continuous integration (with its continuous testing) and continuous delivery (with its associated production monitoring) can eliminate the need for classic regression testing. In addition to advanced strategies like configuration flags and incremental roll-out, Matt describes the change in risks as teams deliver more often, the origins of long regression cycles, and small steps that can have a big impact on software team performance. Leave with examples, stories, things to consider, a possible roadmap—and the information you need to know if the roadmap is worth pursuing.