Seb Rose explores the choices a team needs to make when considering which Agile test practices to adopt, urging teams to practice, practice, practice until they are happy with the way they code.
Paul Grenyer discusses why and how to create a Walking Skeleton - an implementation of the thinnest possible slice of real functionality that we can automatically build, deploy and test end-to-end.
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.
David Starr demoes Pex –a parameterized white box unit test tool- and Moles –an isolation framework-, two .NET tools useful for test-first development.
Ulf Wiger discusses the importance of automated testing along with some lessons learned at Ericsson, including using randomized and extensive testing, aiming to achieve system robustness.
Steve Ross-Talbot presents Savara, comprising a set of tools enabling enterprise architects to validate various artifacts against other artifacts based on the “Testable Architecture” methodology.
Stephanie Forrest believes in the possibility to create evolvable software through automated bug repair, optimizing or improving code and creating new combinations of existing functionality.
Ashish Kumar on how Google keeps the source code of over 2000 projects in a single code trunk containing 100s of M of code lines, with more than 5,000 developers accessing the same repository.
Alois Reitbauer shows how to do performance testing during development, testing, and production by starting early in the development phase, breaking the test into pieces, and testing continuously.
Mobile Testing Challenge: Why Mobile Apps Need Real-World Testing Coverage and How Crowdsourcing Can Help
Doron Reuveni presents how to use crowdsourcing for testing mobile applications, the specific characteristics of the In-the-Wild testing accompanied by a live demo, and some real-world success stories
Simon Stewart presents how Google’s Engineering Productivity team and Software Engineers in Test (SETs) help developers to make their code more maintainable, recommending some of their tools.