A solid test-driven development strategy is a great first step, but the team needs to know if a bug is introduced into code they’ve already written and tested. Although software engineers should be running all unit tests prior to committing any code changes to the source code repository, sometimes things slip through the cracks.

A continuous integration server automatically builds the latest code and runs all of the unit tests,
notifying the team if there were any failures. This session will explain the fundamental concepts of continuous integration, and talk through an example of how this works with one of the latest continuous integration tools: Bitbucket Pipelines.