Utilizing component testing for ultra fast builds

Комментарий Программного комитета:

Во-первых, это доклад про то, как правильно распределять тесты между разными уровнями, в котором ни разу не звучит словосочетание «пирамида тестирования». Во-вторых, в докладе очень много примеров кода, как делать это хорошо. И они базируются на очень большом опыте Тима по работе с различными системами и их тестированием.

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 popular microservice-style architecture, but it also applies to components created in a large monolith or with the out-of-the-box patterns that front-end libraries promote.

If we are able to test the functionality of the component independently, and apply a level of trust that those components work, this opens the door to rethinking Continuous Integration and Continuous Delivery strategy, potentially reducing the need for long test suites and many environments. It will also cause a rethinking of how to unite testing strategy and the test pyramid.

In this talk Tim Cochran will walk you through the different kinds of component testing, show working examples and advise when to apply them. He will also cover what this might mean for your organization's broader testing strategy.