How Google Tests Software
James A. Whittaker
Reading Time
at 250 WPM5h 14m
The average reader, reading at a speed of 250 WPM, would take 5h 14m to read How Google Tests Software.
Personalise your estimate by entering your reading speed below
Test my reading speedEnter speed in words per minute
11
days at 30 min/day
314
total minutes
How Google Tests Software
Published
2012
Publisher
Addison-Wesley
Pages
314
ISBN-13
9780321803023
ISBN-10
0321803027
Description
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.
Subjects
Site Reliability Engineering
Work Rules! Insights from Inside Google That Will Transform How You Live and Lead
The Four
In the plex
Improving online conversions for dummies
How Google Works
Frequently Asked Questions
How many pages are in How Google Tests Software?
This edition of How Google Tests Software has approximately 314 pages. Please note, this is an estimate and the exact page count can vary between hardcover, paperback, and e-book versions.
How long does it take to read How Google Tests Software?
For most readers, How Google Tests Software typically takes between 6h 33m and 4h 22m to complete. This is based on the book's length of approximately 78,500 words and common reading speeds.
Here's a detailed breakdown: • Continuous reading at 250 WPM: approximately 5h 14m of focused reading • Casual reading (30 minutes/day): you could finish in roughly 11 days • Estimated word count: 78,500 words
Your individual reading time will vary based on your personal reading pace, the amount of daily reading time, and your familiarity with the subject matter.
What is the word count of How Google Tests Software?
The estimated word count for How Google Tests Software is approximately 78,500 words. This figure is calculated using industry-standard methods that consider genre-specific word density patterns, typical formatting and layout characteristics, and standard words-per-page ratios for published books.
This is an approximation — actual word count may vary based on font size, formatting, edition, and the presence of illustrations or charts.
Who is the author of How Google Tests Software?
How Google Tests Software was written by James A. Whittaker.
When was How Google Tests Software published?
The publication date for this specific edition is 2012. The original work may have been published on a different date.