Zsolt Fabok presents several methods that can be used to find areas which are worth testing so that organizations do not have to spend more effort on testing than what is absolutely necessary.
John Penix describes the test automation system and the supporting build system infrastructure used by Google.
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.
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.
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-.
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.
Heath Borders introduces several testing tools for iOS - OCUnit, Google Toolbox for Mac (GTM), GHUnit, UISpec, UIAutomation, OCMock – making some recommendations on which is better.