Integration tests are often rife with pitfalls that can result in confusing, flaky, or otherwise completely unmaintainable tests. Those pitfalls can often be mitigated by testing in containers, as this usually provides the most straightforward path to creating ephemeral test environments. Containerized tests typically provide isolation and reproducibility, but they can be costly to initially set up, especially if the system under test is not built for a containerized environment. Nonetheless, there are many benefits to containerized testing, even if the system under test won’t ultimately...
Ryan Hoban
Engineer
Bloomberg
Ryan Hoban is an engineer at Bloomberg, where he works on the company’s Software Security Platform team. He previously worked on Trading Systems, Fixed Income Pricing, and Quality Engineering. A strong advocate for proper testing processes & automation, he has developed several training courses to evangelize a test automation strategy across the organization, including one about integration testing in containers, which is the motivation for this talk. He is a true believer that proper testing is the cure to so many software development headaches, and that a little education about software testing goes a long way.