what happens to testing in continuous delivery?
TRANSCRIPT
How a tester saw it
bla bla bla Test bla
1. Test plan2. Test cases3. Waiting for Specification, Design, Release...
4. Testing5. Change test plan6. Change test cases7. Waiting for ...8.Testing...
Mittwoch, 29. Oktober 2014
How a everyone else saw it
bla bla bla Test blaDesign/ Spec Planning Dev Waiting for
Test Release
QA is a bottleneck
Mittwoch, 29. Oktober 2014
When?
Design/ Spec Planning Dev ReleaseTest
1. Early feedback
2. Analysis/ Requirement sessions
3. User Stories/Accpetance Criteria
early
Mittwoch, 29. Oktober 2014
When?
Design/ Spec Planning Dev ReleaseTest
1. Continuous Integration
2. TDD/ ATDD
3. Priority of tests/ Which tests are important for release goal?
in parallel
Mittwoch, 29. Oktober 2014
When?
Design/ Spec Planning Dev ReleaseTest
1. Observe and measure production
2. Feedback loop
asynchronouscontinuous
Mittwoch, 29. Oktober 2014
Testing is everywhereDesign/
Spec Planning Dev Test Release
Analysis Dev Acceptance Business Check Done
validaterequirements
verifyrequirements
testingautomation
testingautomation
Mittwoch, 29. Oktober 2014
What?When: early, in parallel, ansynchronous, continuouslyWho: Everyone. Tester transform into consultants for every development phaseShared quality responsibilities vs. blame tester
Mittwoch, 29. Oktober 2014
But how?Test plan merges into product goal strategyTest cases merges into user scenariosAcceptance of design/UI/UX is a shared responsibilityTesting is part of the definition of doneReleasing is a team and PO decision
Mittwoch, 29. Oktober 2014
How?
release often
test faster
start earlybe fasterautomate
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
Linkshttp://de.slideshare.net/AlexSchwartz1/bed-con2014-continuousdeliveryundtestenhttp://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