The document provides an overview of modern testing practices, emphasizing the importance of gathering information about quality and risks to aid in product decisions. It discusses the distinction between scripted checking and exploratory testing, as well as the design of tests in an agile context to reduce duplication and enhance collaboration. It highlights the evolving role of testers as designers, experimenters, and facilitators in a code-driven and continuous integration environment.

1. Modern Testing Overview
with LeanDog
INFO@LEANDOG.COM

2. The Purpose
of Testing
INFO@LEANDOG.COM

3. Gather information
about quality & risks
to assist with product decisions
INFO@LEANDOG.COM

4. INFO@LEANDOG.COM
Testing =
Checking + Exploration

5. INFO@LEANDOG.COM
Checking can be scripted.
Exploration is bounded & focused.

6. INFO@LEANDOG.COM
Creating checks
& performing exploration
require a human designer

7. Test Design
INFO@LEANDOG.COM

8. INFO@LEANDOG.COM
Design the checking harness.
Reduce test duplication.
Consider the test pyramid.

9. INFO@LEANDOG.COM
Functional story tests
Unit tests (CFMT)
End-to-end tests
Systems
Integration
Chartered
ExploratoryTesting

10. INFO@LEANDOG.COM
Charter structure:
Explore <area>
with <resources>
to discover <information>.

11. Agile Changes
When & How
Not What
INFO@LEANDOG.COM

12. INFO@LEANDOG.COM
Design tests earlier.
Design tests collaboratively.

13. INFO@LEANDOG.COM
Chartering
Validation
Story Mapping
Three Amigos
Pairing
Swarming

14. INFO@LEANDOG.COM
Execute checks
early and often.

15. INFO@LEANDOG.COM
Explore together frequently.

16. Agile
Testing
Practices
INFO@LEANDOG.COM

17. INFO@LEANDOG.COM
Test automation...
...should be code-based
...not brittle, UI, record/playback

18. INFO@LEANDOG.COM
Test Driven Development - TDD
(code-facing micro tests)

19. INFO@LEANDOG.COM
Collaborative Specification

20. INFO@LEANDOG.COM
Acceptance Test Driven Development
ATDD

21. INFO@LEANDOG.COM
Exploratory Swarming

22. INFO@LEANDOG.COM
Continuous Integration

23. The Evolving Role
of the Tester
INFO@LEANDOG.COM

24. INFO@LEANDOG.COM
Technical awareness.

25. INFO@LEANDOG.COM
Code written by coders.

26. INFO@LEANDOG.COM
No manual script execution.

27. INFO@LEANDOG.COM
Tester as:
designer
experimenter
architect
facilitator
leader

28. Your Deployment
is Software
INFO@LEANDOG.COM

29. INFO@LEANDOG.COM
Your build is your #1 feature.

30. INFO@LEANDOG.COM
Feature branches must die!
(sort of)

31. INFO@LEANDOG.COM
Architect for
feature toggles or
back-to-front deployment.

32. INFO@LEANDOG.COM
Test appropriately
for each environment.

33. INFO@LEANDOG.COM
Test your deployment pipeline.
Check environment & configuration.

34. Questions?
matt.barcomb@leandog.com
INFO@LEANDOG.COM