Exploratory Testing Work Course

Maaret PyhäjärviEmail: <maaret@iki.fi> | Twitter:

maaretp

Testing as Performance (Exploring) vs. Testing as Artifact Creation

4

Realizations about Nature of Testing

2016

1639

5±2

5

20DYNAMICALLY ADAPT FOR LIMITED BUDGET

OPPORTUNITY COST

6

16 EXPECT THEUNEXPECTED

7

1639ROUTES ARE RELEVANT

NOT ALL BUGS ARE EQUAL

8

5±2TAKE NOTES

CREATE CHECKLISTS

Getting Set Up• Google Freemind and download the

latest beta version

Strong Style Pairing“For an idea to go from your head to

the computer it must go though someone else’s hands”

*http://llewellynfalco.blogspot.fi/2014/06/llewellyns-strong-style-pairing.html

Mob Programming Rulesfor Exploratory Testing Activity

• No thinking as the driver• Yes, and…

• Kindness, consideration and respect

Explore with Intent

Mission Charter

Other Charters Details

INTE

NT

LEARNIN

GS

13

Exploratory Testing: Frame of Management

”A day’s work”

Vision (“Sandbox”) Current Charter

Other Charters Details

Bug Reports

Perception of quality

and coverage

Quality ReportDebriefin

g

Tester

Test Manager

PastResultsObstaclesOutlookFeelings

?#

xCharter backlog of the future testing

Out of budget

Next in importanc

e!#, ?, x, +20:20:60

Session sheets of the past testing

Idea of exploratio

n

Metrics summary

Coaching

PlaybooksCoverage outlines

StructureFunction

DataPlatform

OperationsTime

15

Exploration SkillsSource: Adapted from James Bach, Jon Bach, Michael Bolton. Exploratory Testing

Dynamics. v.2.2. 2009

Self-manageme

nt

Developing ideas

Examining product

DoneTo DoIssuesCoverage

All sources available Best use of time – effective and efficient work

Making modelsTool support – creative solutionsRisk-based testing – scientific approachKeeping one’s eyes open

Question, Thoughts?Feedback?