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.
Nathan Peterson introduces Behavior Driven Development, showcasing its adoption by his team along with successes and failures using it.
Matt Wynne presents unwanted patterns one can recognize from his own team, and provides insight on how to fix them.
Marco Vermeulen discusses doing Behaviour Driven Development with Cucumber, Groovy and Grails.
Liz Keogh discusses breaking down requirements without going into too much detail combined with complexity estimation for easy planning, dependency management, and prioritization.
Marco Vermeulen showcases using BDD and Cucumber to develop GVM, an open source tool for managing parallel SDK versions.
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.
Philip Japikse discusses and demoes doing BDD with Context Specifications, then using MSpec to transform those specification into TDD code.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
James Kovacs explains how to use TDD and BDD to focus the architectural efforts on the high-value areas of the code in order to obtain just-in-time software architecture.