The document discusses the impact of continuous delivery (CD) on testing practices, highlighting that testing becomes an integral part of each development phase and is a shared responsibility among all team members. It emphasizes the need for early feedback, continuous integration, and the transformation of testers into consultants. The overall goal is to automate testing processes and release products more frequently for faster learning and improvement.

1. Continuous Delivery
What happens to testing?
Mittwoch, 29. Oktober 2014

2. How much changes
testing with CD?
little much
Mittwoch, 29. Oktober 2014

3. How much changes
testing with CD?
little much dramatic
Mittwoch, 29. Oktober 2014

4. Challenge
Releasing whenever an artefact is finished
Mittwoch, 29. Oktober 2014

5. Looking back
Design/
Spec Planning Dev Test Release
Mittwoch, 29. Oktober 2014

6. How a tester saw it
bla bla bla Test bla
Mittwoch, 29. Oktober 2014

7. How a tester saw it
bla bla bla Test bla
1. Test plan
2. Test cases
3. Waiting for
Specification, Design,
Release...
4. Testing
5. Change test plan
6. Change test cases
7. Waiting for ...
8.Testing
...
Mittwoch, 29. Oktober 2014

8. How a everyone else
saw it
Desbilgan/ bla bla Test bla
Spec Planning Dev Waiting for
Test Release
QA is a
bottleneck
Mittwoch, 29. Oktober 2014

9. How CD changes
testing?
When?
Who?
What?
How?
Mittwoch, 29. Oktober 2014

10. When?
Design/
Spec Planning Dev Test Release
Mittwoch, 29. Oktober 2014

11. When?
Design/
Spec Planning Dev Test Release
1. Early
feedback
2. Analysis/
Requirement
sessions
3. User
Stories/
Accpetance
Criteria
early
Mittwoch, 29. Oktober 2014

12. When?
Design/
Spec Planning Dev Test Release
1.
Continuous
Integration
2. TDD/ ATDD
3. Priority of
tests/
Which tests
are
important
for release
goal?
in parallel
Mittwoch, 29. Oktober 2014

13. When?
Design/
Spec Planning Dev Test Release
1. Observe
and measure
production
2. Feedback
loop
asynchronous
continuous
Mittwoch, 29. Oktober 2014

14. Who?
Mittwoch, 29. Oktober 2014

15. Who?
Everyone!
Mittwoch, 29. Oktober 2014

16. Testing is everywhere
Design/
Spec Planning Dev Test Release
Analysis Dev Acceptance Business
Check Done
validate
requirements
verify
requirements
testing
automation
testing
automation
Mittwoch, 29. Oktober 2014

17. What?
When: early, in parallel, ansynchronous,
continuously
Who: Everyone. Tester transform into
consultants for every development
phase
Shared quality responsibilities vs. blame
tester
Mittwoch, 29. Oktober 2014

18. But how?
Mittwoch, 29. Oktober 2014

19. But how?
Test strategy = Continuous Delivery
Mittwoch, 29. Oktober 2014

20. But how?
Test plan merges into product goal
strategy
Test cases merges into user scenarios
Acceptance of design/UI/UX is a shared
responsibility
Testing is part of the definition of done
Releasing is a team and PO decision
Mittwoch, 29. Oktober 2014

21. What happens to
testing?
Analysis Dev Acceptance Business
Check Done
Mittwoch, 29. Oktober 2014

22. How?
release
often
test
faster
start early
be faster
automate
If I am getting
faster in testing I can
release more often!
If I am releasing
often I can learn how to
improve faster!
Mittwoch, 29. Oktober 2014

23. Links
http://de.slideshare.net/
AlexSchwartz1/bed-con2014-
continuousdeliveryundtesten
http://dannorth.net/blog/
http://www.agile42.com/en/blog/
2013/11/04/agile-testing-days-2013-
tomasini/
http://gojko.net/category/
Mittwoch, 29. Oktober 2014