While some developers may find it silly to create tests they know will immediately fail, this is actually the first step of test-driven development. Test-driven development not only results in better code, it also reduces those late night surprises when it comes to deploying the software. All developers know that they should adopt test-driven development practices, so why are so few actually doing it? The short answer is that it sucks writing tests. The goal of this talk is to demonstrate some of the tools that make test-driven development [somewhat] bearable on OpenStack environments. In this talk, join Hart Hoover as he: