starwest workshop: explore with intent

@maaretp http://maaretp.com

Exploratory Testing Explore with Intent

by Maaret Pyhäjärvi


Exploratory Testing

learning while testing


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


Exploratory testing is a systematic approach for discovering risks using

rigorous analysis techniques coupled with testing heuristics.


Realizations on Nature of Testing

20 16

1639 5±2 6


20 DYNAMICALLY ADAPT FOR LIMITED BUDGET OPPORTUNITY COST

7


16 EXPECT THE UNEXPECTED

8


1639 ROUTES ARE RELEVANT NOT ALL BUGS ARE EQUAL

9


5±2 TAKE NOTES CREATE CHECKLISTS

10


Product is my external imagination

I am my developer’s external imagination


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

the code. - Adapted from James Bach


Intent the art of expressing

what you want


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


Strong-Style Pairing Exercise


Highest level of abstraction

Intent Location Details


Explore with Intent

mechanism of continuous planning


"All the brilliant people working on the same thing, at the same time, in

the same space, on the same computer." -- Woody Zuill

Lets Test!


Activity: Exploring part 1

• Find the Happy Path: why would anyone want to use this? • Retrospective: What have we

learned?


Discuss Observations Retrospective

Using Stickies


Theory to take home


Explore with Intent

Mission Charter

Other Charters Details

INT

EN

T

LEA

RN

ING

S



• Coverage: Identify what is there • Retrospective: What have we

learned?



Using Mindmap


Theory to take home


Exploratory Testing: Frame of Management

”A day’s work”

Vision (“Sandbox”) Current Charter

Other Charters Details

Bug Reports

Perception of quality and coverage

Quality Report Debriefing

Tester

Test Manager

Past Results Obstacles Outlook Feelings

? #

x Charter backlog of the future testing

Out of budget

Next in importance!

#, ?, x, +

20:20:60

Session sheets of the past testing

Idea of exploration

Metrics summary

Coaching

27

Playbooks

Coverage outlines


Exploration Skills Source: Adapted from James Bach, Jon Bach, Michael Bolton. Exploratory Testing Dynamics. v.2.2.

2009

Self-management

Developing ideas

Examining product

Done To Do Issues Coverage

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

Making models Tool support – creative solutions Risk-based testing – scientific approach Keeping one’s eyes open

28



• Bug reporting: RIMGEA • Retrospective: What have we

learned?



Using Mindmap


Theory to take home


R Replicate I Isolate M Maximize G Generalize E Externalize A and say it clearly and

dispassionately


Example blog-while-testing

http://visible-quality.blogspot.fi/2015/06/blog-while-testing-experiment-of-way-to.html


Learning about a Feature Getting Started


Learning about a Feature Setting up for Testing


Learning about a Feature Remembering Connections


Learning about a Feature Reading the Spec


Learning about a Feature Coming up with Connections


Learning about a Feature Focus to Actually Start


Learning about a Feature Software Talks


Observations from Learning about a Feature

•  I chose my focus – Specification first vs. Experiencing the feature first

•  Found and logged bugs –  Jira, stopped and wrote a proper report that

slowed me down

•  Ended up with open questions – Work done creates more work

There’s no right / wrong

focus


Summing it Up Learning in Layers http://visible-quality.blogspot.fi/2015/06/blog-while-testing-experiment-of-way-to.html


(Exploratory) Tester

(Application) Programmer

Test Automator / Programmer


Three ways of Scoping

More ways of Managing


Disposable test automation


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)