Fabrizio Romano proposes using TDD to transform business requirements into tests, driving code and tests development in harmony.
Seb Rose discusses BDD, what it is good for and what tools can help, common BDD anti-patterns and myths, as well as advice for starting with it.
Pawel Sawicz suggests putting tests to the test by mutating the code to see if the codebase is properly covered by tests and how errors are propagated.
Russ Miles shows how we can build production-level confidence in our polyglot microservices by applying the test-driven approach to synchronous (REST) and asynchronous (Messaging) services.
In this talk Alan Blount gives a quick overview of the main categories of testing and how they may apply to various web application projects.
Nathan Peterson introduces Behavior Driven Development, showcasing its adoption by his team along with successes and failures using it.
Felienne Hermans presents various algorithms that outlining the power of Excel, showing that spreadsheets are fit for TDD and rapid prototyping.
Matt Wynne presents unwanted patterns one can recognize from his own team, and provides insight on how to fix them.
Kevlin Henney advises on writing Good Unit Tests (GUTs) by treating testing as a form of communication with multiple levels and forms of feedback.
Marco Vermeulen discusses doing Behaviour Driven Development with Cucumber, Groovy and Grails.
Mark Seemann uses F# to demonstrate how to use functional design with TDD to remove the need for Mock objects.
James Grenning takes a look at why the technical practices of TDD, refactoring, continuous design, clean code and automated testing can help people and their organization be great.