Here’s a preview of the on-demand webinar “Exploratory Testing for Agile & Continuous Testing”. Watch the complete webinar to learn how exploratory testing can increase the effectiveness of your agile and continuous testing processes. If you want help recording exploratory testing actions, documenting exploratory testing results, and collaborating with others on exploratory testing, start a free trial of Tricentis Tosca. This industry-leading solution integrates exploratory testing with automated testing, risk-coverage optimization, test data design & management, and more. Watch the webinar: https://www.tricentis.com/resource-assets/webinar-2017-01-18-exploratory-testing-for-agile-and-continuous-testing-usa/ Start a free trial: https://www.tricentis.com/tricentis-tosca-testsuite/trial/

1. Ingo Philipp
© 2016 by .
Exploratory Testing
For Agile & Continuous Testing

2. © 2016 by
Agenda
1. Why you should go for it?
2. What is exploratory testing?
Common confusions, misconceptions & controversies.
Relation & distinction to other approaches.
3. Who should do it?
4. How to practice it?
Heuristics & techniques.
5. When to practice it?
How to integrate it into the software lifecycle?

3. © 2016 by
Historical Context
2016
Is the term a source of
inspiration or confusion?
Is it an activity or a technique?
Is it something that you do?
A way or style of doing something?
Is it an approach?
Isn’t then all testing
exploratory testing?
Is the term helping or
hurting the testing craft?
2010
2000
1988
Recognition
Controversy
Hostility
Tolerance
Acceptance
Cluelessness
Ignorance
Nescience
Unawareness
Cem Kaner, Testing Computer Software
*Glenford J. Myers, The Art of Software Testing, 1979

4. Sprint
Start
Sprint
End
PackageBuild 2
N-1 N
NN-1
Unit & Smoke Tests
1 2
1
Regression Tests
User Story
Sprint Acceptance Test
One
Day
Life-Cycle Integration
Exploratory
Session
Test Case
Design
Automation

5. Sprint
Start
Sprint
End
2
User Story
Life-Cycle Integration
1.What should be explored?
Business Use Case, System Use Case, Epic, Theme, User Story, Technical Component, …
2. What are the core characteristics?
Performance, Usability, Stability, Security, Safety, Reliability, Understandability, …
3. Which tour(s) are required?
Supermodel Tour, FedEx Tour, Money Tour, Landmark Tour, </ Custom Tour/>, …
4. Which hat(s) should be considered?
Black Hat, White Hat, Red Hat, Green Hat, Yellow Hat, </ Custom Hat />
5. Who is required, and who takes which hat?
6. Who owns the session(s)?
7. How long should the session(s) last?
1 2
1
Exploratory
Session