2. Exploratory Testing
Un-scripted – The script is not designed prior to testing but in
parallel to testing in what is known as Session Notes.
The term Exploratory Testing was coined by Cem Kaner in 1983.
An approach to software testing which is concisely described as
simultaneous learning, test design and test execution.
3. Busting the Myths about ET.
ET is unstructured – Is disciplined, Structured
and has a mission.
Is performed after the
test execution phase –
A parallel activity including learning about the
system/product under test, test design and
test execution.
Has no test cases – Comprises of test ideas.
And no documentation – Has documentation.
5. Introduction to SBTM
Session Based Test Management
Terminologies used: SBTM – MBTS
What is SBTM?
Managing testing by dividing testing into
chunks of time called sessions.
Session notes are maintained as Session logs.
6. Session Log
Session log is the documentation which states what is tested , how and when.
Mission
Date & Start Time
Estimated Time
Testers Involved
Environment, Platform & Version
Session Notes
Memory of a Bug – If the tester decides to log the bugs outside of the session
time, then the session log serves as a 'memory' of a bug.
7. Why Debrief ??
Debrief often t0 share and learn from
Bug reports
Investigation reports
Findings
Observations
Questions
Experience reports
Tools used
Debriefing can help acquire domain knowledge faster by collaborating with other
testers.
8. Questions?
Is SBTM applicable to projects of any domain
and every scale?
Answer for yourself!
do NOT fall prey to dogma.
9. Where to from here: Learn about ET
http://www.satisfice.com/articles/what_is_et.shtml
http://www.satisfice.com/tools/procedure.pdf
Network to learn from and with the community of
global testers.
Stop at nothing….
10. Introducing Change in your Testing
Department.
Here is an interesting series by Bernice Ruhland
on ‘Introducing Session-Based Testing To Your
Team’
http://
media.wix.com/ugd/c47e45_8c6a76d9da034e16990
