As i read in this book, Patrick Copeland is a senior director at Google's Engineering Productivity.
Jason Arbon ia a test engineer and Jeff Carollo ia a software engineer at Google.
This book prepared by this crew.
http://www.amazon.com/Google-Tests-Software-James-Whittaker/dp/0321803027/ref=sr_1_6?s=books&ie=UTF8&qid=1335000331&sr=1-6
When you start to read, you couldnt stop reading this book until the last page.
Sometimes you feel reading a periodical paper, sometimes a book :).
Chapters have many different styles from each other.
Test approach, test automation methods of Google are detailed.
They shared interviews with Google Colleagues about their test methodologies, methods, tools in the software engineering(Q&A style).
You can find the answer the "What Noogler means?" question :).
According to book:
Quality is not equal to Test and explains the differences and relations between Q&T.
How many different test layers are used by engineers are detailed in this book.
You can learn how "Crawl-->Walk-->Run" is summarized the from canary to release lines.
Some of the clauses that underlined by me as follows:
"All engineers must reuse existing libraries unless they have very good reason not to based on a Project specific need."
"Dependencies must be seriously and especially with common code...."
and importance of readibility is explained in this section.
"Keeping it simple and uniform is a specific goal of the Google Platform."
"Life of Bug" section is interesting. Which Bugs are the heartbeat and workflow for software quality that you learn in the another section.
And what's next?--> i recommend you reading this book.
Before & After this book:
Visit this Good blog: Sometimes you feel reading a book again when you surf on this blog.
http://googletesting.blogspot.com/
If it is possible join this conference:
GTAC is the Google Test Automation Conference (http://www.gtac.biz/).