Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Defects are expensive
Examples Financial Bank: EUR 300.000
Web travel agency: EUR 200.000
80% Software Dev dollars on defects
Solving trivial bugs
1. Developer writes code and tests
2. Tester finds defect and logs
3. Developer tries to reproduce
4. Developer finds bug and investigates
5. Team discussion about how it should work
6. Developer re-codes, re-unit-tests, re-builds,
re-delivers
7. Tester verifies and closes ticket
We let bugs happen
Requirements
Software Development
Quality Control
Bugs
We need change!
Re
qu
irem
en
ts Ma
turity
Th
ree
Am
igo
me
etin
g
A
cc
ep
tan
ce
Driv
en
De
ve
lop
me
nt
In
Flig
ht U
I Re
vie
w
P
air P
rog
ram
min
g
Q
ua
lity W
itho
ut
co
mp
rom
ise
C
on
stan
t Fe
ed
ba
ck
D
eliv
er V
alu
e
Where do defects come
from?
Where do defects come
from?
Software development
Quality Control
User Experience
Requirements
Deliver the right code / functionality from the start
Stop the presses!Don’t make assumptions
Miscommunication
Misunderstanding
Value people and interaction
over documents
Requirement maturity
Testable and estimable?
User Story short enough?
UI elements defined?
Business rules defined?
Customer acceptance Tests defined?
Three Amigos meetings
Create one vision
One Vision
Product Owner
Tester
Developer
Three Amigos meetings
Discover unknowns
What does the requirement mean?
What are the special cases?
How will we test this?
What about the non-functions?
What to do with errors?
Deliver value in stead of
Burning Tasks
Plan Build Test Review Deploy
Huh?
We’re getting
wet…
Get Test Infected!
Test Driven
DevelopmentQuality comes first
Build test
Build feature
Refactor
Functional
Test Driven Development
Build test
Build feature
Refactor Build test
Build feature
Refactor Build test
Build feature
Refactor
Why Functional Testing?
Stable code Desired Functionality
What is the functionality?
Testing Pyramid ROI
Agile Testing Quadrants
In Flight UI ReviewDon’t wait until the end of the
sprint to get feedback
Study in Pair programming
Goal:
Build product in 45min
15 programmers
5 working alone
10 in 5 (swapping)
pairs
Study in Pair programming
Time
Study in Pair programming
Test Cases passed
Study in Pair programming
ENJOY
Study in Pair programming
Lines of code
Pair programming
Bad attitude Good attitude
Quality comes from within
Quality
Commitment
Responsibility
Confidence
Continuous Improvement
Working together
Exploratory Testers
Communication
Be curious about how stuff is tested by Programmers
Partner with Programmers
Coach Test Awareness / Test infection
Programmers
Communication
Ask Testers for help
Show Testers what’s build / tested
Help out with Automation
What are we doing here?
It’s NOT Testing
It’s NOT Coding
....
It’s Software Development
Nope
Bugs in production
are normalTry to minimize them ASAP
Related Documents
