06 Exploratory Testing
06 Exploratory Testing
Specialisten in vooruitgang
Exploratory testing in
theory and practice
Jan Jaap Cannegieter
Principal consultant Squerist
Wendbaar-
Specialisme Mens op 1
heid
1
8-5-2019
Test diensten
Test partnership
Specialisten in vooruitgang
Why testing?
2
8-5-2019
€ 6.522.600.000
3
8-5-2019
I want to
prevent this Studenten van de TU Delft die
onvoldoendes voor vakken hebben
gehaald hebben toch een diploma
gekregen. Dit komt door een
softwarefout in de systemen
De fout is ontstaan door een softwarefout.
Volgens de bank komt dit door een fout bij een
leverancier. De klanten halen massaal hun
spaargeld weg bij de bank. Dit is niet nodig,
aldus een woordvoerder van de bank. “alle
klanten worden schadeloosgesteld” aldus de
woordvoerder. , NIBC probeert al jaren een
positie op de consumentenmarkt probeert te
krijgen. Dit helpt daar niet bij.
Exploratory testing
10:30
4
8-5-2019
Test management
Strategy &
planning
Design &
TP 3
Execution Closure
Specification
TP 4
TP 2
Test point
10
10
5
8-5-2019
TP 3
TP 4
TP 2
11
11
Or populair said
12
12
6
8-5-2019
Simultanuous working
Execution Learning
Strategy
(thinking)
13
13
Optional discussion
What are the possible benefits of exploratory testing compared to scripted
testing?
What are the possible backdraws of exploratory testing compared to
scripted testing?
14
14
7
8-5-2019
15
16
16
8
8-5-2019
Case PHPTravels
Go to www.phptravels.net
This is a test system!
14:00
17
15:30
18
9
8-5-2019
13:30
19
20
20
10
8-5-2019
From
To
21
Sessions (timebox)
Mission
Test charters
Test points
Session notes
Session debrief
Metrics
22
22
11
8-5-2019
Session
Timebox
60 min. – 90 min. – 120 min.
Short enough to report in detail
Short enough to plan it easily
Long enough to test in depth
Long enough to debrief effectively
Don’t make a detail planning of the session
Eventually pair testing
Tester – tester
Tester – product owner
Tester – user
Tester – developer
23
23
Test mission
24
24
12
8-5-2019
Test charter
Also named a session sheet
Information of the test item
Mission
Test points
Information about the test execusion (optional)
Defects (or references to the defects in the tool)
New test charters or new test points
See example
25
25
26
26
13
8-5-2019
Session notes
What did I test?
What didn’t I test?
Why did I test it?
How did I test it?
With which coverage and depth did I test it?
Which test data did I use?
On which environment did I test?
What have I found out?
What defects did I find?
What more should I test?
27
27
Defects
Questions
Possible new charters
Possible new points
Tests that should be automated
Tests that should be documented
Instructions for the next time this charter will be executed
28
28
14
8-5-2019
Session debrief
Mission
Risks Coverage
Techniques Environment
Test session
29
29
Focus - defocus
30
30
15
8-5-2019
Discipline - freedom
31
31
16:00
32
16
8-5-2019
33
Scripted Exploratory
Category Situation testing testing
Documentation A lot and detailed documentation
Little documentation
Constantly changing doc./req.
System Waterval
Agile
Budget A lot of budget
Little budget
Time Early involved
Late involved
A lot of time available
Little time available
Test skills Analytical, accurate testers
Critical thinking (question everything)
Flexible
Professional testers
Non-professional testers 34
34
17
8-5-2019
35
18