Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
How Google Tests Software
Search
Sponsored
·
SiteGround - Reliable hosting with speed, security, and support you can count on.
→
Rex Chung
March 30, 2013
Technology
700
5
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
How Google Tests Software
Summary of learnings from the book.
Rex Chung
March 30, 2013
Transcript
24 slides
HOW GOOGLE TESTS SOFTWARE
OVERVIEW 1. Ideologies 2. Roles 3. Methodologies 4. Types of
tests 5. Tools 6. Roles for us.
IDEOLOGIES Entire team is responsible for quality.
IDEOLOGIES Entire team is responsible for quality. Google engineers prefer
quality over features.
IDEOLOGIES Entire team is responsible for quality. Google engineers prefer
quality over features. Optimize for both quality and speed.
IDEOLOGIES Entire team is responsible for quality. Google engineers prefer
quality over features. Optimize for both quality and speed. Quality != Test
IDEOLOGIES Entire team is responsible for quality. Google engineers prefer
quality over features. Optimize for both quality and speed. Quality != Test Quality is not important until the software is important
ROLES Engineering Productivity Team Software Engineer Software Engineer in Test
Test Engineer Test Director
ENGINEERING PRODUCTIVITY "overcome bias against testing and a company culture
that favored heroic effort over engineering rigor."
SOFTWARE ENGINEER fault tolerant designs failure recovery TDD unit tests
SET Review designs Check code quality and risk Refactor code
to make it more testable. Write testing frameworks and automation.
TE User focused Product experts Quality advisers and analyzers of
risk. Write automation scripts. Coordinate with contract testers, dogfooders and beta users etc.
METHODOLOGIES Make testing a feature Centers around Code Review Single
Repository CI with submit queue Test suite - Parallel on single machine.
TYPES OF TESTS Small Medium Large (Enormous)
SMALL All mocked, no http or database calls Ideally 100ms
< 1 min 70%
MEDIUM Database, localhost calls Ideally 1 sec < 5 mins
20%
LARGE Allowed to call external service Focus on user's expectation
< 1hr 10%
TOOLS Test Analytics ACC (Attribute Component Capability) Google Test Case
Manager Manual test cases, Exploratory testing Buganizer Triage, accountability, reports, search before filing Record Playback Framework record and generate selenium tests.
TEST ANALYTICS
BUGS Severity: how much it affects functionality. Priority: how soon
it should be fixed.
ROLES FOR US SWE == SET Team Lead =~ TE
(Test Engineering Designer) Devops = Engineer Productivity + Tooling
TE DESIGNER Test design and coordination Identify resources required for
testing.
ENCOURAGE TESTING OKRs Certification program (test coverage, test speeds, 0
flaky tests, automated smoke test etc).
NEXT Things we can do to improve quality More resources
http://googletesting.blogspot.com/
Other Decks in Technology
See All in Technology
CloudTrail を推したい
kazzpapa3
1
160
Kansai WordPress Meetup@大阪『ブロックテーマを作る上で知っておくべきこと
torounit
0
290
Web Performance Is a Journey [PerfNow 2026]
tammyeverts
2
120
gradle-best-practices 使ってみた
mikanichinose
0
220
攻撃と守りは何が変わり、何が変わらないのか~最近の不正アクセスから考える、リスク評価と標準の使いどころ
oidfj
2
300
20261119_AgentCore
takuyay0ne
1
180
Context parameters で作る!はじめての型クラス
kworkdev
PRO
1
170
AWS Blocksで AIエージェント作れるの知ってます?
kmiya84377
1
160
農家は秘伝のタレを知らない - NOBODY KNOWS THE HIDDEN SOURCE - Kaggriculture 3rd Place Solution
masspeaks
3
670
「個社」ではなく「業界」の課題を解く AI 対話開発 ー 価値を広げる設計と、価値を守るエンジニアリング ー
ivry_presentationmaterials
4
840
AI-Ready なデータ基盤ってなに? & 新卒未経験が、いま考えていること
imuta
0
1.1k
飯から始まるデータエンジニア
sansantech
PRO
0
130
Featured
See All Featured
Leveraging Curiosity to Care for An Aging Population
cassininazir
1
570
Building Flexible Design Systems
yeseniaperezcruz
330
41k
The Pragmatic Product Professional
lauravandoore
37
7.5k
ラッコキーワード サービス紹介資料
rakko
5
6M
Data-driven link building: lessons from a $708K investment (BrightonSEO talk)
szymonslowik
1
1.4k
Joys of Absence: A Defence of Solitary Play
codingconduct
1
580
Writing Fast Ruby
sferik
630
63k
StorybookのUI Testing Handbookを読んだ
zakiyama
31
7.1k
From Legacy to Launchpad: Building Startup-Ready Communities
dugsong
0
380
Large-scale JavaScript Application Architecture
addyosmani
516
110k
Leveraging LLMs for student feedback in introductory data science courses - posit::conf(2025)
minecr
1
480
[RailsConf 2023] Rails as a piece of cake
palkan
59
7.2k