REVIEW - How Google Tests Software

Title:

How Google Tests Software

Author:

James A. Whittaker, Jason Arbon, Jeff Carollo

ISBN:

0321803027

Publisher:

Addison-Wesley Professional (2012)

Pages:

281pp

Reviewer:

Paul Floyd

Reviewed:

April 2014

Rating:

★★★☆☆

Reviewed: January 2014

There are some technical books that read a bit like a novel. Then there are some that read like an encyclopaedia. And again there are some that read like a collection of short stories. This book is a collection of bits and bobs that clearly falls into the last category. There’s a lot about Google and the Google culture – in part the book reads like an advert for Google hiring and required reading for newly inducted Google testers.

The book gives an overview of the people (SETs, basically a developer/tester role and TEs, test engineers) that are behind the testing. Tools are covered, without going into too much detail. I must say that I envy the Google CI system. Selenium/WebDriver gets quite a few mentions, which I suppose makes sense as it is close to their core business.

Whilst I wasn’t expecting the book to literally fit its title and explain the Google systems in detail, I do think that a bit more structure would have helped. There are bits that feel like someone took their Dictaphone to the coffee machine and left it on while a gang of people were chatting casually. Then again, perhaps that’s how things are inside Google.


Book cover image courtesy of Open Library.