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.
Alex Aitken and Nick Faulkner share lessons learned building a cross-platform HTML5 application based on GOOS principles (Growing Object-Oriented Software).
Cory Maksymchuk introduces 3 patterns for writing cleaner code: Predicates, Classifiers, and Transformer.
Doug Hiebert discusses the principles and objectives behind automated testing, TDD, Unit and Integration Testing, using asserting and mocking to write tests, and static analysis.
Phil Nash discusses the challenges and practical consideration regarding doing TDD on mobile devices, providing advice for such development on iOS.
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.
Keith Braithwaite conducts a tutorial class on TDD based on the following technique: Add a test, See it fail, Make all tests pass, Refactor, and Repeat until done.
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.