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.
James Kovacs discusses using TDD and BDD to avoid complexity and creating evolving architectures where convention is emphasized over configuration.
Tom Sulston explains how to manage systems with Cucumber and Puppet based on BDD principles, including practical tricks and pitfalls. The session demoes using those tools.
Jason Gorman presents how developers can learn TDD to the point of transforming the knowledge acquired into habits by exercising a number of practices followed by peer evaluation.
Nat Pryce exemplifies how he dealt with flickering, false positives, slow, and messy tests appearing in asynchronous testing when trying to perform end-to-end testing.
John Hughes shows how to explore the bugs of a code by creating a series of tests in Erlang and using multiple test frameworks, discovering the faults and evaluating the frameworks while doing it.
Robert C. Martin on writing good code starting with a bad code example, then addressing many topics like: Boy Scout rule, functions, arguments, craftsmanship, TDD, engineering, certification, etc.
Ben Hall shows how Ruby testing tools can help with .NET and ASP.NET development and takes a look at RSpec, Webrat, Cucumber, Selenium and others. Also: a peek at using IronRuby for testing .NET apps.
Steve Freeman offers advice on writing good tests that make development easier avoiding dead weight code that is hard to maintain. Topics: readability, complex data, diagnostics, and flexibility.
Dan North gives an overview of Domain Driven Design and Behavior Driven Development then ties them together for a powerful mix.