Loading presentation...
Prezi is an interactive zooming presentation

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start 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.

DeleteCancel

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.

No, thanks

How releasing faster changes testing?

Presented at the conference Agile Testing Days 2012 (www.agiletestingdays.com) in Potsdam
by

Alex Schwartz

on 27 April 2017

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of How releasing faster changes testing?

releasing
How
changes
testing
faster
Testing in
production

Automate
The hen and egg problem
releasing
faster
testing
faster
What comes first?
Canary
Testing
More
Testing
Test
Driven
Source:
Michael Nygard, "Disband Deployment Army",
goto Aarhus 2012
http://www.flickr.com/photos/the_sprouts/4981153823
http://gotocon.com/dl/goto-aar-2012/slides/MichaelT.Nygard_DisbandTheDeploymentArmy.pdf
Understand Risk Better
Obvious: We cannot release more often
without testing more quickly.
Question:
How we can learn how to do testing more quickly without having the pressure?
Why this talk?
fair
How
much
is releasing faster
changing testing?
not at all
a lot
dramatically
up side down
Less Testing
Risk Based
Testing
Early Feedback
Test faster
= scale out
Lower Quality?
more
people
more
machines
Async
Testing
Shared Responsibility
No QA Team
test-driven
tests
deployments
full pipeline
infrastructure
...
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 ....
the
customer impact
- 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
P_error probability
C_event cost per event
Reduce
Minimizing costs of an event
Source: Michael Nygard, "Disband Deployment Army", goto Aarhus 2012
Rhythm
Not all activities can be aligned with the release rhythm.
Examples: security review, initial tests, etc.
Idea:
Use comprehensive testing for your full value stream in order to save time.
My experience:
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
Motivating Examples
(Adrian Cockcroft, goto Aarhus 2012)
e. g.
- 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!
Thank you!
RESTful API
PBAPI: Circuit Breaker
system A
system C
observe requests
in case of problems:
connection to optional upstream system
answer with less content
detect
resolve
scope of impacted
time to resolve (MTTR) = cylce time
time to detect (MTTD)
RESTful API
PBAPI: Automated Error Reporting
Analytics
log/scribe
report job
file all 5xx
codes
maps every request to a known bug or files a new bug
upstream
downstream
Circuit Breaker
Test requests in prod
Alex Schwartz
Alex Schwartz
Nokia
Location & Commerce
Agile Coach
Programmer
1990
2011
Startup
2008
mobile.de (eBay)
Head of a DevOps team
2004
Startup
alexander.schwartz@nokia.com
https://twitter.com/alexschwartzbln
http://de.linkedin.com/in/alexanderschwartzberlin
https://www.xing.com/profile/Alexander_Schwartz7
Sr. Programmer
Tech Lead
Release Manager
Agile Test Manager
The mobile.de (eBay) Continuous Delivery Story
2 years: improvements step by step
earlier
Async
The Challenge
Disclaimer:
This is all based on my personal experience.
in my context.
release
Hardening/Test Phase
Development Phase
Deploy
Challenge:
There is no longer time for testing.
Hardening/Test Phase
Development Phase
Deploy
faster/
scale
Wall to Ops
Wall to QA
Full transcript