Agile Serbia: Exploratory Testing Explained and Experienced

@maaretp http://maaretp.com

Exploratory Testing Explained and Experienced

by Maaret Pyhäjärvi


TESTING IS ABOUT FEEDBACK:

QUALITY-RELATED INFORMATION


Testers don’t break the code, they break your illusions about

the code. - Adapted from James Bach


Realizations on Nature of Testing

20 16

1639 5±2 4


20 DYNAMICALLY ADAPT FOR LIMITED BUDGET OPPORTUNITY COST

5


16 EXPECT THE UNEXPECTED

6


1639 ROUTES ARE RELEVANT NOT ALL BUGS ARE EQUAL

7


5±2 TAKE NOTES CREATE CHECKLISTS

8


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


What Testing gives Us U

nit T

estin

g

Expl

orat

ory T

estin

g

SPEC FEEDBACK REGRESSION GRANULARITY

GUIDANCE UNDERSTANDING

MODELS SERENDIPITY Testing as

artifact creation

Testing as performance


Product is my external imagination

I am my developer’s external imagination


Learning in Layers A Demonstration of Exploratory Testing


Teaching Exploratory Testing in a Mob


Strong-Style Navigation

“For an idea to go from your head to the computer it must

go through someone else’s hands”

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


Observations Retrospective

ONE IDEA PER STICKY

NOTE

CAPITAL LETTERS

EASY TO

READ

FEW WORDS

Lowercase letters

Don’t write in cursive or in biro

Avoid writing too much on one single note as it takes a while for people to

read the whole thing!

•  IDEA 1 •  IDEA 2 •  IDEA 3

≠

≠

≠

≠



Before implementing

While implementing

Before production

While in production

Testing as artifact creation

Testing as performance (exploration)

Ways to think of testing peak at different moments with regards to adding a capability

TOTALS

Testing is Everywhere!


Maaret Pyhäjärvi Email: [email protected] Twitter: @maaretp Web: maaretp.com Blog: visible-quality.blogspot.fi (please connect with me through Twitter or LinkedIn)

Software

Agile Serbia: Exploratory Testing Explained and Experienced