Using Component Testing for Ultra-Fast Builds

[presentation]
by
Timothy Cochran
Summary: 

A best practice of software architecture is to design your applications into independent modules or components, with a published contract for interaction between components. This is a principle of the microservices style of architecture, but it also applies to components created in a large monolith. If we can test the functionality of the component independently, and apply a level of trust that those components work, this opens the door to rethinking our continuous integration and continuous delivery strategy, potentially reducing the need for long test suites and many environments. It will also cause us to rethink our unit testing strategy and the test pyramid. Tim Cochran will talk through the different kinds of component testing, show working examples, and give advice about when to apply them. He will also cover what this might mean for your organization's broader testing strategy. You will leave with an understanding of a component testing strategy, examples of testing front-end and back-end components, and an approach to adjusting your organization's CI strategy to take advantage of components tests.

Tags: 
About the Presenter

Tim Cochran  currently works for ThoughtWorks NYC, and has been full stack developer and architect for over 15 years. Working on everything from large distributed enterprise projects to small NGO visualization apps. He recently has been helping companies with digital transformation, moving towards continuous delivery and building a DevOps culture. He also is an automated testing zealot, practices TDD almost exclusively, he builds test strategy using the right combinations of unit, E2E and functional testing for clients.

Upcoming Events

Apr 19
May 03
Jun 07
Oct 04