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.
Alois Reitbauer shows how to do performance testing of complex software systems during development, testing, and production by starting early in the development phase, breaking the test into pieces, and testing continuously. He also shows how to perform scalability tests on limited hardware or by using the cloud.
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 in different ways - scripted/exploratory, on device/off device, automated/manual -, the specific characteristics of the In-the-Wild testing accompanied by a live demo, and some real-world success stories.
Simon Stewart presents the activity of Google’s Engineering Productivity team and the role Software Engineers in Test (SETs) play in helping software developers to make their code more maintainable, recommending some of their tools: Gold linker, Eclipse, distcc, JDepend, graphviz.
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 critical solar system exploration missions.
Sam Newman discusses how to improve the process going from software development to production, covering the following steps: building, configuration, automated testing, deploying, monitoring, logging and disasters. He 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.