Dmytro Mindra discusses the tools and practices used for a game engine: Unit Testing and Test automation, Unity Runtime Test Framework, Continuous Integration, Game Test Framework, Performance Tests.
Patrick Smacchia shares code analysis-related practices -structuring code, measuring code quality, automated tests, code contracts, reporting progress, trending- based on his experience with NDepend.
Janet Gregory explains how testing activities are included throughout the Agile process, and how a tester can add value, discussing ATDD (Acceptance Test Driven Development), and exploratory testing.
John Hughes discusses automated testing techniques that can catch more code defects, with war stories from the likes of Ericsson, Volvo Cars, and Basho Technologies.
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, an open source project comprising from a set of tools enabling enterprise architects to validate various artifacts against other artifacts built in different phases of the development process based on the “Testable Architecture” methodology.
Stephanie Forrest believes in applying evolutionary biology principles to the software process creating evolvable software through automated bug repair, improving code and creating new combinations of existing functionality.
Ashish Kumar presents how Google manages to keep the source code of all its projects, over 2000, in a single code trunk containing hundreds of millions of code lines, with more than 5,000 developers accessing the same repository.