The document discusses agile development practices and test automation. It notes that manual testing and batch testing are outdated approaches. It promotes test automation for unit tests and integration tests as well as exploratory testing to balance learning about unknowns and making knowledge explicit. The document encourages participants to provide feedback in an evaluation booklet to help the presenter learn.

1. Markus Gärtner
@mgaertne
it-agile GmbH
Agile Dev Practices – 5th March 2013

3. “Too
old
they
are.“

4. Batch-Testing

5. Pipelining

6. Pipelining

10. http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfall.pdf

11. http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfall.pdf

12. Manual Testing

16. Test Automation
UI
„Integration“
Tests
Unit-Tests

30. Opportunity Costs
Any time spent on test automation is time
not spent on learning about unknowns.
Any time spent on Exploratory Testing is
time not spent on making knowledge
explicit.

31. Bring Balance to the Force

32. Questions?
You know, you have this
evaluation booklet in your
conference bag.
Please do me the favor to
put something in there about
the stuff that you heard and
saw. It will help me know
more of the stuff that I don‘t
know.