ACCU Home page ACCU Conference Page
Search Contact us ACCU at Flickr ACCU at GitHib ACCU at Google+ ACCU at Facebook ACCU at Linked-in ACCU at Twitter Skip Navigation

Search in Book Reviews

The ACCU passes on review copies of computer books to its members for them to review. The result is a large, high quality collection of book reviews by programmers, for programmers. Currently there are 1918 reviews in the database and more every month.
Search is a simple string search in either book title or book author. The full text search is a search of the text of the review.
    View all alphabetically
Title:
How Google Tests Software
Author:
James Whittaker, Jason Arbon, Jeff Carollo
ISBN:
0-321-80302-7
Publisher:
Addison Wesley (2012)
Pages:
320pp
Price:
£
Reviewer:
Paul Floyd
Subject:
Review and Testing
Appeared in:
25-6

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.