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.
Gerard Holzmann discusses Spin, a design analyzer tool, and Scrub, a code review tool, used by Jet Propulsion Laboratory to analyze and fix the software used for solar system exploration missions.
Sam Newman offers practical advice on how to avoid transforming the development, QA and Operations into silos by using build pipelines providing continuous builds and deployment.
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.