Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
How releasing faster changes testing?
Transcript of How releasing faster changes testing?
The hen and egg problem
What comes first?
Michael Nygard, "Disband Deployment Army",
goto Aarhus 2012
Understand Risk Better
Obvious: We cannot release more often
without testing more quickly.
How we can learn how to do testing more quickly without having the pressure?
Why this talk?
is releasing faster
not at all
up side down
= scale out
No QA Team
Given team A can fix a bug in 30 days,
and team B in 120 minutes.
Which team has to test more?
The impact of a bug is ....
- which grows over time.
test the right stuff
expected losses from undesirable events
Loss = N_events × P_error × C_event
Loss annual loss
N_events number of events
C_event cost per event
Minimizing costs of an event
Source: Michael Nygard, "Disband Deployment Army", goto Aarhus 2012
Not all activities can be aligned with the release rhythm.
Examples: security review, initial tests, etc.
Use comprehensive testing for your full value stream in order to save time.
Adapting testing for C.D.
means much more than testing faster,
it requires a major mindshift.
Integrate Testing in Development
Focus on cylce time
Track timing of customer transactions thru full stack
(Adrian Cockcroft, goto Aarhus 2012)
- profile your
app in prod
Please evaluate the presentations and use for this the evaluation booklets which you can find in your conference bag.Thank you!
PBAPI: Circuit Breaker
in case of problems:
connection to optional upstream system
answer with less content
scope of impacted
time to resolve (MTTR) = cylce time
time to detect (MTTD)
PBAPI: Automated Error Reporting
file all 5xx
maps every request to a known bug or files a new bug
Test requests in prod
Location & Commerce
Head of a DevOps team
Agile Test Manager
The mobile.de (eBay) Continuous Delivery Story
2 years: improvements step by step
This is all based on my personal experience.
in my context.
There is no longer time for testing.
Wall to Ops
Wall to QA