Page 1
Modern Testing Overview
(YOU CAN CHANGE THIS IMAGE)
with LeanDog
[email protected]
Page 2
The Purposeof Testing
(YOU CAN CHANGE THIS IMAGE)
[email protected]
Page 3
Gather informationabout quality & risks
to assist with product decisions
[email protected]
Page 4
[email protected]
Testing = Checking + Exploration
Page 5
[email protected]
Checking can be scripted.
Exploration is bounded & focused.
Page 6
[email protected]
Creating checks& performing explorationrequire a human designer
Page 7
Test Design
(YOU CAN CHANGE THIS IMAGE)
[email protected]
Page 8
[email protected]
Design the checking harness.
Reduce test duplication.
Consider the test pyramid.
Page 9
[email protected]
Functional story tests
Unit tests (CFMT)
End-to-end tests
SystemsIntegration
Chartered Exploratory Testing
Page 10
[email protected]
Charter structure:
Explore <area>with <resources>
to discover <information>.
Page 11
Agile Changes When & How
Not What
(YOU CAN CHANGE THIS IMAGE)
[email protected]
Page 12
[email protected]
Design tests earlier.
Design tests collaboratively.
Page 13
[email protected]
Chartering
Validation
Story Mapping
Three Amigos
Pairing
Swarming
Page 14
[email protected]
Execute checksearly and often.
Page 15
[email protected]
Explore together frequently.
Page 16
AgileTesting
Practices
(YOU CAN CHANGE THIS IMAGE)
[email protected]
Page 17
[email protected]
Test automation...
...should be code-based
...not brittle, UI, record/playback
Page 18
[email protected]
Test Driven Development - TDD(code-facing micro tests)
Page 19
[email protected]
Collaborative Specification
Page 20
[email protected]
Acceptance Test Driven DevelopmentATDD
Page 21
[email protected]
Exploratory Swarming
Page 22
[email protected]
Continuous Integration
Page 23
The Evolving Roleof the Tester
(YOU CAN CHANGE THIS IMAGE)
[email protected]
Page 24
[email protected]
Technical awareness.
Page 25
[email protected]
Code written by coders.
Page 26
[email protected]
No manual script execution.
Page 27
[email protected]
Tester as:
designerexperimenter
architectfacilitator
leader
Page 28
Your Deploymentis Software
(YOU CAN CHANGE THIS IMAGE)
[email protected]
Page 29
[email protected]
Your build is your #1 feature.
Page 30
[email protected]
Feature branches must die!(sort of)
Page 31
[email protected]
Architect forfeature toggles or
back-to-front deployment.
Page 32
[email protected]
Test appropriatelyfor each environment.
Page 33
[email protected]
Test your deployment pipeline.
Check environment & configuration.
Page 34
Questions?
(YOU CAN CHANGE THIS IMAGE)
[email protected]
[email protected]