How Google Tests Software

Seamless delivery of cloud software at scale is a massive challenge, but one company has largely surmounted it: Google. In reaching this goal, a state-of-the-art testing process was of paramount importance. This book offers an unprecedented "under the hood" look at how Google tests its cloud software, introducing never-before-revealed best practices for testing and automation. Test pioneer James Whittaker and two Google testing experts bring together powerful lessons, place them in perspective, and codify them for use by any practitioner. They offer candid insights into what's working for Google - and an insider's skeptical look at processes that aren't yet working optimally. Along the way, they offer readers a solid foundation for making decisions about: * Risk analysis and test planning * Thinking like the user (and knowing which user!) * Exploratory, black box, white box, and acceptance testing * Incorporating community feedback * Tracking issues more effectively * Using off-the-shelf tools, custom tools, spreadsheets, and dashboards * Understanding the lives of software engineers and test engineering managers * Testing early "Docs and Mocks" * Testing interfaces, classes, modules, libraries, binaries, services, and infrastructure * Managing code reviews * Performing small, medium, and large-scale tests * Refactoring * Using test hooks, presubmit scripts and queues, and continuous builds * Deployment and production monitoring and more

James Whittaker: James is an Engineering Director at Google and has been responsible for testing Chrome, maps, and Google web apps. He used to work for Microsoft and was a professor before that. James is one of the best known names in testing. Jason Arbon: Jason is a Test Engineer at Google and has been test lead for Google Desktop, Chrome, and Chrome OS and development lead for an array of open source test tools. He worked at Microsoft prior to joining Google. Jeff Carollo: Jeff is a Software Engineer in Test and has focused on developer tools for code presubmit testing. He has consulted with dozens of internal Google development teams helping them improve initial code quality. He converted to Software Engineer in 2010 and leads development of Google+ APIs.