EuroSTAR Software Testing Conference 2009 presentation on Introducing Exploratory Testing to Save the Project by Johan Jonasson . See more at conferences.eurostarsoftwaretesting.com/past-presentations/

1. Introducing Exploratory Testing
To Save The Project
Johan Jonasson
johan.jonasson@houseoftest.se

2. What is Exploratory Testing?
As a term, coined by Dr. Cem Kaner, elaborated on by
James Bach, Michael Bolton and countless others.
Simultaneous learning, test design and execution.
No documented step-by-step test cases.
Emphasis on time spent testing, rather than planning,
designing and documenting.
Exploratory testing values the tester’s skill, critical
thinking and ability to find bugs.
The exploratory tester’s ability to come up with good
tests usually increases over time.

3. purely
scripted tests
freestyle
explorationchartered
explorationvague
scripts
fragmentary
test cases
role-based
exploration
Levels of Exploration

4. Session-Based Test Management
Undocumented testing = low accountability?
Session-Based Test Management is laying
accountability groundwork through:
Charter
Time Box
Reviewable Results
Debriefing

5. Defects
Issues
Coverage
Notes
Charter
Defect
Defects
Issues
Coverage
Defects
Issues
Session-Based Test Management

6. The Context
Multinational product and service company
Bulky processes and ways of working.
Strong focus on quantitative metrics and testing against
explicit requirements.
Project setup
Inexperienced team
Sketchy requirements
Tight budget
Narrow time plan
Product aimed at consumer market

7. Original plan

8. Forming a backup plan
Testing aims to provide quality-related information.
Best effort with available resources.
Focus on basic stability.
Risk analysis input for exploratory test missions.
Moving away from confirmatory testing (checking)
towards testing in the ”putting to the test” sense.

9. Building the team
Iterative process integration instead of big bang.
Pilot team consisting of the most curious testers rather
than the most experienced.
Get comfortable with way of working.
Do not fall into documentation over testing trap.
Start with high level of free-style exploration based on
high abstraction mission statements.
Develop and share heuristics within the team.
Gradually introduce and encourage increased note
taking and documentation on-the-go.

10. The Outcome
Confidence in product design.
Lessons learned
Management support
Workshops
Proof of concept
Positive approach side-effects
Checking is boring, exploring is fun!
Challenges testers’ cognitive abilities.
Super-charges test team morale.
Introducing testers to agile development team.

11. johan.jonasson@houseoftest.se
+46 702 98 97 20
http://www.houseoftest.se
http://www.twitter.com/johanjonasson
Web
Mobile
E-mail
Twitter
Thank you!
Johan Jonasson
House of Test Consulting AB