Jason Felice introduces TDD, how it came about, the two schools of TDD thought, the differences and contradictions between them.
Wojciech Seliga shares from experience how complex it can be to deal with thousands of tests -unit, functional, integration, performance- for Atlassian JIRA and what they did to bring it under control.
Ian Cooper reminds what was Kent's original proposition on TDD, what misunderstandings occurred along the way and suggests a better approach to TDD, one that supports development rather impeding it.
Scott Ambler explains the pros/cons of daily just-in-time architectural modeling and a TDD approach to design level, advising through examples on integrating these techniques into development.
Marco Vermeulen showcases using BDD and Cucumber to develop GVM, an open source tool for managing parallel SDK versions.
Bryan Beecham teaches the TDD principles with LEGO bricks, making technical concepts easier to grasp by working with your own hands.
Marco Vermeulen explains using Cucumber and Groovy to apply BDD to a project, using Gherkin for writing scenarios, Groovy for step definitions, Spock for new features, and running Cucumber features.
Liz Keogh shows why conversations are the most important aspect of BDD, how examples can help you discover things early, and why discovery is an inevitable part of software development.
Sandro Mancuso runs a hands-on demo adding tests to a Java legacy code then refactoring it.
Zsolt Fabok provides guidance on selecting those sections of code that are most likely to profit from automated testing and leaving out those where chances for errors are low.