Continuous Testing (CT) is a developer practice that shortens the feedback loop established by Test Driven Development. It gives you near instant feedback about the correctness of your code, and helps you find bugs as quickly as syntax errors. This session will cover how CT has evolved in the last year, it’s current capabilities, and limitations. The presenters will also show several demos of the practice using freely available continuous testing tools, and examine how these tools can be integrated with existing infrastructure to bring the benefits of CT to a wider audience.

This talk focuses around a series of diagrams that help explain how various practices work.

Many practices work to different degrees of success depending on exactly how they’re implemented. We’ll discuss why this is so, with examples of multiple ways to do pair programming, testing, and planning. Along the way, we’ll show some new work: how to get a better plan by not estimating, models to identify which practices to experiment on, and how to find what to vary.

Each concept will be explained with diagrams that get to the gist of the practice - and methods of thinking about variations.