Talk presented at the Agile Tour Vienna 2016 conference. http://agiletourvienna.at/#scheduleModal-does-agile-mean-we-have-less-time-for-testing ABSTRACT: In the last decade, the speed of our industry has increased greatly. Agile Development, DevOps and Continuous Delivery are the main drivers for this paradigm shift which has now become widely accepted. Ten years ago, it was common to only release a couple of new versions a year. Today, there are companies delivering hundreds of software deployments per day. This isn’t only true in IT, but also e.g. for Tesla-Automobile, which delivers its software updates a few times a week. Where does quality happen when we’re releasing this often? Is it possible to have proper quality management and is there enough time for testing? How can we reduce what could be weeks of testing to deliver new features to our clients on a daily basis? Alex is a long-term enthusiast for this topic. Based on his experiences with various products and companies, he’ll share his insights into the mystery of “faster testing”. The key questions are: - When – When do we test? - What – What should we test? - Which quality aspects are important? - How – How do we test? Which techniques are helpful? - Who – Who is involved in testing, test automation, etc.? - How much – How much should we test? Furthermore, we discuss the financial benefits of Agile Testing and aiming for Continuous Quality. Last but not least we explore if it only exists in fairy tale land or if it is real.

15. Smoke Test + Dashboard

25. Alex Schwartz
Source:
Lisa Crispin & Janet Gregory
Agile Testing: A Practical Guide for Testers and Agile Teams
.

26. Recipe: The “Tetris Principle” -Test as low as possible
Story: As a customer I can contact the seller of an interesting ad.
Risk/aspect 1
Mail is not sent
due to config
problems
Risk/aspect
Layout of mail
is crap
Risk/aspect:
Wrong mail
language
Risk/aspect:
Javascript problem
in contact form
no automated tests
automated tests
Story Test / UI
(Integration)
Story test
below UI
Story Test / UI
(Browser)

39. Mein Erfahrung
...
100%
DevOps-Team “Places” bei
Verbesserungen
Fire Fighting
Deployment / Liefern
10 Monate 20 Monate
(mit Cloud)
...

43. Alex Schwartz
Principle: Visibility
www.flickr.com/photos/shannonsturgis/4274202367
Sonntag, 10. Oktober 2010 KW

44. Alex Schwartzwww.flickr.com/photos/28549294@N05/4273275734
Analogy #1:The Definition of Done (DoD) in a Kitchen
Assume a professional cook in a
restaurant kitchen is asked to
create a nice meal for a customer.
When it’s DONE?
NO
Sonntag, 10. Oktober 2010 KW

45. Alex Schwartz
Goal: A happy kitchen crew
www.flickr.com/photos/fractalv/1341923133
Sonntag, 10. Oktober 2010 KW

47. dback
Zeit (MTTR)
Kosten
ren
in Stufen)
rs über die
eller als
st doppelt
eben (MTTR):
edarf
e Fehler
zu spät
und
zu teuer
schnell
behoben
StundenMonateTageWochen

48. dback
Zeit (MTTR)
Kosten
eren
in Stufen)
rs über die
eller als
st doppelt
eben (MTTR):
edarf
e Fehler
zu spät
und
zu teuer
schnell
behoben
StundenMonateTageWochen
gray team
has half of
the bug
backlog of
the blue team
team
“blue”
team
“gray”