Join BookitisSave favorites, build lists, and follow creators.

How Google Tests Software

Work detail

Bookitis Pick
Cover for How Google Tests Software
HG
Image source: Open Library
James A. Whittaker1 editions

Hundreds of millions of lines of code distributed across billions of source files. Billions of build actions prompting millions of automated tests daily. Hundreds of thousands of browser instances daily. Apps released at a continuous pace. Ladies and gents, it doesn't get more difficult than this (at least not by much). About the Authors 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 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 is a Software Engineer in Test and has focused on developer tools for code presubnnit 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.

Overview

Shared work-level identity and catalog context.

1 credited authorSearch language english

Bookitis keeps work pages focused on the shared book identity and the editions that actually belong to it. Unrelated books should not appear here as primary content.

Contributors

People credited with this work in the active catalog.

  • James A. Whittaker

    Author profile in the active Bookitis catalog

    Open Author

Editions

Publication-specific versions linked to this work only.