Home > Store > Process Improvement
How Google Tests Software
- By James A. Whittaker, Jason Arbon, Jeff Carollo
- Published Mar 23, 2012 by Addison-Wesley Professional.
- Copyright 2012
- Dimensions: 7" x 9-1/4"
- Pages: 320
- Edition: 1st
- Book
- ISBN-10: 0-321-80302-7
- ISBN-13: 978-0-321-80302-3
Register your product to gain access to bonus material or receive a coupon.
Product Author Bios
James Whittaker is Director of Test Engineering for Google. He pioneered model-based testing, developed the acclaimed runtime fault injection tool Holodeck, and was an early leader in penetration testing. He has authored or co-authored How to Break Software, How to Break Software Security, How to Break Web Software, and Exploratory Software Testing. Jason Arbon leads test engineering/automation for Google's Chrome Browser and Chrome OS. At Microsoft, he worked on search, BizTalk, and Exchange Server. Jeff Carollo, Senior Software Engineer in Test at Google, now works on Chrome and Chrome OS.
2012 Jolt Award finalist!
Pioneering the Future of Software Test
Do you need to get it right, too? Then, learn from Google. Legendary testing expert James Whittaker, until recently a Google testing leader, and two top Google experts reveal exactly how Google tests software, offering brand-new best practices you can use even if you’re not quite Google’s size…yet!
Breakthrough Techniques You Can Actually Use
Discover 100% practical, amazingly scalable techniques for analyzing risk and planning tests…thinking like real users…implementing exploratory, black box, white box, and acceptance testing…getting usable feedback…tracking issues…choosing and creating tools…testing “Docs & Mocks,” interfaces, classes, modules, libraries, binaries, services, and infrastructure…reviewing code and refactoring…using test hooks, presubmit scripts, queues, continuous builds, and more. With these techniques, you can transform testing from a bottleneck into an accelerator–and make your whole organization more productive!
Downloads
Download free art files for How Google Tests Software here
Related Articles
Seven Ways to Find Software Defects Before They Hit Production
Three Things I Learned about Testing at Google that Might Surprise You
|
43 of 44 people found the following review helpful
Fascinating, but less useful than I had hoped, By
This review is from: How Google Tests Software (Paperback)
When I found out about the book "How Google Tests Software", it didn't take long until I had ordered a copy. I find it quite fascinating to read about how Google does things, whether it is about their development process, their infrastructure, their hiring process, or, in this case, how they test their software. I am a developer at heart, but I have worked for a few years as a tester, so testing is also dear to me.It's quite an interesting book, and it makes some great points about the future of testing. However, despite the phrase "Help me test like Google" on the cover, it is not as useful as I had hoped when it comes to improving your own testing.The book starts off by describing the key roles at Google: SWE (Software Engineer), SET (Software Engineer in Test) and TE (Test Engineer). Briefly, the SWE builds features for Google's products, the SET develops testing infrastructure and larger-scale automatic tests, and the TE tests the products from a user's perspective... Read more
17 of 23 people found the following review helpful
Not very useful book for Software Engineer, By Jack Daniels (San Francisco, CA) - See all my reviews
This review is from: How Google Tests Software (Paperback)
I think this book is not very useful book for Software Engineer. I expected to see more of what I can do better as a Software Engineer to increase quality of my code through testing and what to suggest my QA team to improve process of testing. In that regard first 3 chapters were somewhat interesting to read because it gave me ideas how I can change process of testing in my company, what tools I can use and etc. The rest of the book is just chat about duties of different roles in test (including management) and interviews with Google's employees.I think this book will be more interesting to non-technical people such as managers of different levels so they can brag about "their" thoughts how to improve QA process in their companies on meetings :) So overall I can't say the book is bad. But problem is that Whittaker says quality of the code is responsibility of Software Engineer yet he doesn't provide much insight what Google's SWEs do to take care of... Read more
4 of 5 people found the following review helpful
I Learned Some Things, By Randy Rice "Software Testing Consultant & Tra... (Oklahoma City, OK) - See all my reviews
This review is from: How Google Tests Software (Paperback)
The main question you may be asking is "Why do I care how Google tests software if I'm not a start-up or a development company?" Great question!While your situation will likely not be the same as Google's, there is a lot to be learned in how they do things in development and testing. That's because they seem to have the secret formula in getting features to market quickly and with good quality. Not only did this book give me ideas about how to make testing software more productive, it can give anyone a perspective of software testing not found anyplace else. Most other books address testing from the perspective of "Here's how testing should be performed." This book comes from the angle of "Here's how we do testing." There is a big difference. It is tempting to skip the preface and introduction when reading a book. However, these provide critical context and a good summation of what you can expect to take away from the book. You will see... Read more |
Online Sample Chapter
Introduction to Google Software Testing
Sample Pages
Download the sample pages (includes Chapter 1 and Index)
Table of Contents
Foreword by Alberto Savoia xiii
Foreword by Patrick Copeland xvii
Preface xxiii
Chapter 1: Introduction to Google Software Testing 1
Quality?Test 5
Roles 6
Organizational Structure 8
Crawl, Walk, Run 10
Types of Tests 12
Chapter 2: The Software Engineer in Test 15
The Life of an SET 17
Development and Test Workflow 17
Who Are These SETs Anyway? 22
The Early Phase of a Project 22
Team Structure 24
Design Docs 25
Interfaces and Protocols 27
Automation Planning 28
Testability 29
SET Workflow: An Example 32
Test Execution 40
Test Size Definitions 41
Use of Test Sizes in Shared Infrastructure 44
Benefits of Test Sizes 46
Test Runtime Requirements 48
Case 1: Change in Common Library 52
Test Certified 54
An Interview with the Founders of the Test
Certified Program 57
Interviewing SETs 62
An Interview with Tool Developer Ted Mao 68
An Interview with Web Driver Creator Simon Stewart 70
Chapter 3: The Test Engineer 75
A User-Facing Test Role 75
The Life of a TE 76
Test Planning 79
Risk 97
Life of a Test Case 108
Life of a Bug 113
Recruiting TEs 127
Test Leadership at Google 134
Maintenance Mode Testing 137
Quality Bots Experiment 141
BITE Experiment 153
Google Test Analytics 163
Free Testing Workflow 169
External Vendors 173
An Interview with Google Docs TE Lindsay Webster 175
An Interview with YouTube TE Apple Chow 181
Chapter 4: The Test Engineering Manager 187
The Life of a TEM 187
Getting Projects and People 189
Impact 191
An Interview with Gmail TEM Ankit Mehta 193
An Interview with Android TEM Hung Dang 198
An Interview with Chrome TEM Joel Hynoski 202
The Test Engineering Director 206
An Interview with Search and Geo Test Director
Shelton Mar 207
An Interview with Engineering Tools Director
Ashish Kumar 211
An Interview with Google India Test Director Sujay Sahni 214
An Interview with Engineering Manager Brad Green 219
An Interview with James Whittaker 222
Chapter 5: Improving How Google Tests Software 229
Fatal Flaws in Google’s Process 229
The Future of the SET 231
The Future of the TE 233
The Future of the Test Director and Manager 234
The Future of Test Infrastructure 234
In Conclusion 235
Appendix A: Chrome OS Test Plan 237
Overview of Themes 237
Risk Analysis 238
Per-Build Baseline Testing 239
Per-LKG Day Testing 239
Per-Release Testing 239
Manual Versus Automation 240
Dev Versus Test Quality Focus 240
Release Channels 240
User Input 241
Test Case Repositories 241
Test Dashboarding 241
Virtualization 241
Performance 242
Stress, Long-Running, and Stability 242
Test Execution Framework (Autotest) 242
OEMs 242
Hardware Lab 242
E2E Farm Automation 243
Testing the Browser AppManager 243
Browser Testability 243
Hardware 244
Timeline 244
Primary Test Drivers 246
Relevant Documents 246
Appendix B: Test Tours for Chrome 247
The Shopping Tour 247
The Student Tour 248
Suggested Areas to Test 248
The International Calling Tour 249
Suggested Areas to Test 249
The Landmark Tour 249
Suggested Landmarks in Chrome 249
The All Nighter Tour 250
Suggested Areas to Test 250
The Artisan’s Tour 251
Tools in Chrome 251
The Bad Neighborhood Tour 251
Bad Neighborhoods in Chrome OS 251
The Personalization Tour 252
Ways to Customize Chrome 252
Appendix C: Blog Posts on Tools and Code 253
Take a BITE out of Bugs and Redundant Labor 253
Unleash the QualityBots 255
RPF: Google’s Record Playback Framework 257
Google Test Analytics—Now in Open Source 260
Comprehensive 260
Quick 260
Actionable 260
Sustained Value 260
Index 265
This book includes free shipping!
This book includes free shipping!
eBook (Watermarked)
$27.99
$22.39
Includes EPUB, MOBI, and PDF
About eBook Formats
This eBook includes the following formats, accessible from your Account page after purchase:
EPUBThe open industry format known for its reflowable content and usability on supported mobile devices.
MOBIThe eBook format compatible with the Amazon Kindle and Amazon Kindle applications.
PDFThe popular standard, used most often with the free Adobe® Reader® software.
This eBook requires no passwords or activation to read. We customize your eBook by discretely watermarking it with your name, making it uniquely yours.
- Request an Instructor or Media review copy.
- Corporate, Academic, and Employee Purchases
- International Buying Options
Get access to thousands of books and training videos about technology, professional development and digital media from more than 40 leading publishers, including Addison-Wesley, Prentice Hall, Cisco Press, IBM Press, O'Reilly Media, Wrox, Apress, and many more. If you continue your subscription after your 30-day trial, you can receive 30% off a monthly subscription to the Safari Library for up to 12 months. That's a total savings of $199.
