How Google tests software
by James A. Whittaker
- 0 Ratings
- 8 Want to read
- 2 Currently reading
- 1 Have read
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.
Check nearby libraries
Buy this book
Previews available in: English
Showing 1 featured edition. View all 1 editions?
| Edition | Availability |
|---|---|
1
|
aaaa
Libraries near you:
WorldCat
|
Book Details
Table of Contents
Edition Notes
Includes bibliographical references and index.
Classifications
The Physical Object
ID Numbers
Source records
Community Reviews (0)
Feedback?Lists
See All-
My Offline Library
from alexdd8248
-
Testing
from Jens Dibbern
| December 12, 2022 | Edited by MARC Bot | import existing book |
| March 17, 2022 | Edited by ImportBot | import existing book |
| August 2, 2020 | Edited by ImportBot | import existing book |
| November 26, 2012 | Edited by Abhiram Upadhya | Added some description |
| February 1, 2012 | Created by LC Bot | import new book |