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
Juicy Slices of Testing
Search
Jace Browning
March 23, 2016
Programming
160
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Juicy Slices of Testing
GR Testers discussion slides on different ways to classify testing.
Jace Browning
March 23, 2016
More Decks by Jace Browning
See All by Jace Browning
HTMX + Django
jacebrowning
0
190
Python Packaging and Distribution
jacebrowning
0
120
Best Practices for Automated Regression Testing
jacebrowning
0
180
Skillet pitch at Startup Weekend
jacebrowning
0
220
Continuous Deployment using GitHub, CircleCI, and Heroku
jacebrowning
0
250
Standalone Python Programs using PyInstaller
jacebrowning
0
150
Intro to Make
jacebrowning
0
100
Continuous Deployment: Biography of a Feature Request
jacebrowning
0
140
From Code to Production
jacebrowning
0
130
Other Decks in Programming
See All in Programming
AI時代のシニアエンジニアとは
yosuke_furukawa
PRO
14
11k
Groovy as a human and AI friendly programming language
paulk
0
180
Crash Auto Pipelines
veronikapj
1
350
Goコンパイラを作ってGoをもっと理解する / Build a Go compiler to better understand Go
ikura_hamu
0
120
FactoryBotをやめればRSpecは速くなるのか?
yuta_onishi_97
0
1.5k
Vapor Mode でアクセシビリティは 壊れないか検証した話
fuqda
1
320
AmebaブログはKMPから卒業します
kmars0605
0
320
AIで開発が速くなった先で、開発チームは何を目指すか
shihochan
1
2k
ChromeでローカルLLM
ryu1013
0
190
Python Lambdaにおけるテストしやすい設計とAI支援の活用 / Designing Testable Python Lambda Functions with AI
kitano_yuichi
1
290
LLM 101
dalinaum
0
470
[JA] Domain Modeling with Vanilla Rails: 「操作」から再考するRailsの設計論
yasaichi
4
1.8k
Featured
See All Featured
Utilizing Notion as your number one productivity tool
mfonobong
4
640
Documentation Writing (for coders)
carmenintech
77
5.6k
Claude Code のすすめ
schroneko
67
230k
Crafting Experiences
bethany
1
420
Designing Experiences People Love
moore
143
24k
How To Stay Up To Date on Web Technology
chriscoyier
790
250k
WENDY [Excerpt]
tessaabrams
14
40k
Product Roadmaps are Hard
iamctodd
55
13k
A brief & incomplete history of UX Design for the World Wide Web: 1989–2019
jct
2
560
Into the Great Unknown - MozCon
thekraken
41
2.8k
[Rails World 2026] Durable orchestration on Rails: from continuation to workflow
palkan
2
1.2k
Jess Joyce - The Pitfalls of Following Frameworks
techseoconnect
PRO
1
470
Transcript
Juicy Slices of Testing Jace Browning
Goals • Reach a common understanding of terminology • Share
the diverse, often conflicting approaches to testing • Debate the balance of testing vs. experimentation
Terminology
Quality is value to some person. - Jerry Weinberg
A bug is something that bugs somebody who matters. -
James Bach
Testing is an empirical, technical investigation conducted to provide stakeholders
with information about the quality of a product. - Cem Kaner
Disciplines
Quality Assurance Quality Control
Product Owner Developer Tester
Production Alpha Beta
Scopes
System Function or Method Component
End-to-End Testing Unit Testing Integration Testing
Production Development Machines Staging / QA Environment
Defects
Functional Defects Code Defects Intention Defects
Usability Security
Approaches
Black Box White Box
State-based Testing Interaction-based Testing
Test-driven Development Behavior-driven Development
Exploratory Automated Scripted
Goals
Smoke Testing Sanity Testing
Exploratory Testing Acceptance Testing Regression Testing
Stress Testing Performance Testing Load Testing
Metrics
Feature Coverage Code Coverage Requirements Coverage
Defect Counts?
Summary • Who does the testing? • What do we
test? • What are we looking for? • Which approaches are best suited for a product? • How can we measure our results?