The Awkward Teenager of Testing: Exploratory Testing

Adopting an Exploratory Testing Framework by Shawn Faunce

We think we understand that awkward teenagerMany experienced testers will claim exploratory testing expertise, but too few have ever written an exploratory testing charter, and even fewer have applied a heuristic in that charter. We think we understand exploratory testing just as we think we understand teenagers, because “we have been there”. However the reality is that many of the words currently used in exploratory testing are foreign to us and we feel awkward about our lack of knowledge. This talk is about transforming a traditional testing into an exploratory awesome test team.

Tested = Checked + Explored

Charters

Target Areas

Reso

urce

s

Discovery

Mind M

aps

EcoSystem Heurist icsG o l d i l o c k s

Follow the DataNouns and Verbs

Sta rva t i on

Reconnaissance Charter

A c t i v e R e a d i n g Ambi

guity

Ana

lysis

Risk Heuristics

ReviewingCharters

Resources

TargetAreas

ToDiscover

Planning

Mind Maps EcoSystemHeuristics

BugReports

Framework

FindSomeone

Who Cares

Sourceof

Truth

Feedback

Tools

Learning

Cadence

Start Here

Vent

ure f

orth

Charters ResourcesTargetAreas

ToDiscover

Start with a Framework

Gives us a common, light-weight, solid foundation from which to venture forth

“Charters, We don’t need no stinking charters!”

- Cheech (or was it Chong ?)

A Spot, not a journey

Consistent naming

You must plan You must think

You seek treasures not defects

Improvementshere had

the biggestimpacts

Learning Reviewing

Adopt a Cadence

As you evolve through experimentation, cadence is your control variable to measure results.

Our crystal ball was surprisingly accurate

“What I learned yesterday” – what a difference a word makes

Adopting new practices only once a week

Planning

Improvementshere had

the biggestimpacts

Heuristics EcoSystem

Grab some Tools

Learning tools is an investment, invest in yourself because no else will

Conversation Starters

No one else is looking at the system this way

Few people have all the keys to the kingdom, be one of the few

Mind Maps

Improvementshere had

the biggestimpacts

Sourceof

Truth

FindSomeone

Who Cares

Bi-Directional Feedback

Feedback is a two-way street, you can be a consumer as well as a producer

The most interesting defects we find are neighbors of latest fix

Getting past the “that was the requirement” defense

They exist, you need persistence

BugReports

Improvementshere had

the biggestimpacts

Notes From the TrenchesChallenges and solutions transitioning a traditional test team into an exploratory test team on a large, heavily interfaced system.

I’ve a feeling we’re not in Kansas anymoreChallenge: Changing a mindset Solution: Framework, cadence, training, discussions, and metrics

Why do you want access to my system?Challenge: You need “visas” to exploreSolution: You need allies, and strong ones

Yet another build!!!?Challenge: Continuous Delivery means continuous deploymentsSolution: Test in parallel with and after production deployments

What is truth?Challenge: Acceptance criteria vs. Desired OutcomeSolution: Find someone who cares

Boldly going where no one has gone beforeChallenge: Indigenous population may be indigentSolution: “Marketing” brochure and chocolate chip cookies

References

3 Titans:• Elisabeth Hendrickson• James Bach• Cem Kaner

Elisabeth HendericksonHendrickson, Elisabeth, Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing

James Bachhttp://www.satisfice.com/blog/archives/category/exploratory-testing

Cem Kanerhttp://www.kaner.com/pdfs/QAIExploring.pdf