Dave Hart introduces the “developer in test” role more testing at the unit level and adding a level of testing between unit and system, and providing testing frameworks for regression system testing.
Jonathan Lipps introduces Selenium, a functional testing framework, discussing and demoing how Selenium is used in the automated testing stack, then shares some gotchas and best practices.
Yehoram Shenhar and Alistair McKinnell present a way of doing testing having every team member involved in planning, estimating, and defining tests, testability being an architectural system attribute.
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.
Daniel Spiewak and Aaron Bedra take a look at code verifying starting with Tony Hoare’s paper on testing(1969), type theory, and language-integrated proof systems.
Gareth Rushgrove offers advice, code samples, and introduces tools - Puppet, Chef and CloudFormation – helpful for automating every infrastructure operations.
Mike Andrews discusses architecting for failure even you when don’t know what might fail.
Julian Harty covers various challenges and practices for testing applications for mobile devices.
Karl Krukow discusses the importance of automated functional testing of native mobile applications, suggesting using Calabash –a Cucumber-like tool- and LessPainful –an online testing service-.
Baruch Sadogursky demonstrates automated building techniques using Maven/Gradle/Custom scripts and Binary Repository along with common pitfalls that are to be avoided.
Roberto Salama presents a regression testing framework built at Morgan Stanley with FitNesse, Scala, and KDB/Q, and used to run over 10,000 regression tests.