A Taste of Exploratory Testing

Preview:

DESCRIPTION

An introduction to Exploratory Testing by Anne-Marie Charrett

Citation preview

copyright ©TestingTimes 2013

A TASTE OF EXPLORATORY TESTING

Anne-Marie Charrett@charrett

Skype: Charretts Blog: Mavericktester.com

This work is licensed under the Creative Commons Attribution-NoDerivs 3.0 Unported License. To view a copy of this license,

visit http://creativecommons.org/licenses/by-nd/3.0/.

copyright ©TestingTimes 2013

IRISH CREDENTIALS

• Born in St Michaels Dun Laoghaire

• Lived in Dublin and Leixlip (officially Co.Kildare)

• Studied at Kevin Street, DIT

•Worked for EOLAS, Government Standards Body

• Holidays, in County Kerry.

copyright ©TestingTimes 2013

UNPREDICTABLE CLIMATE

• “When all is said and done, the weather and love are the two elements about which one can never be sure.” Alice Hoffman

copyright ©TestingTimes 2013IMPROVISATION

copyright ©TestingTimes 2013

copyright ©TestingTimes 2013

CONCLUSION

IRISH MAKE THE BEST TESTERS

copyright ©TestingTimes 2013

A TASTE OF EXPLORATORY TESTING

Anne-Marie Charrett

copyright ©TestingTimes 2013

TEST COIN FLIP FREE

Any questions?

copyright ©TestingTimes 2013

DISCUSSION

•What bugs did you find?

•What do you do ?

copyright ©TestingTimes 2013

BUGS

copyright ©TestingTimes 2013

WHAT DID YOU DO?

• Played around

• Tried out different things

• Figured out how it worked

• Saw something unusual - looked more

• Read up the information (on Website)

• Compared your findings

copyright ©TestingTimes 2013

SCRIPTED TESTING

Requires a tester to be able to:

Often has formalised methodology based on IEEE829

Design Test Scripts upfront against Requirements

Requires Experienced Test Analyst Vs Tester

Indicate Expected Result upfront

Complete when 100% Test Executed

Aims to be repeatable

Agile - > automated checking

copyright ©TestingTimes 2013

Test Strategy Test Spec Test Execution

Analysis

Documents

Design Testing

Activities

SCRIPTED TESTING

Test Report

Strategy

Modelling

Decision Making

ModellingConfiguration

OperationObservationEvaluation

Configuration

Reporting

OperationObservationEvaluation Communicationcopyright ©TestingTimes 2013

copyright ©TestingTimes 2013

“Exploratory testing is an approach to software testing that is concisely described as simultaneous learning, test design and

test execution.” Cem Kaner

“The plainest definition of exploratory testing is test design and test execution at the same time.” J. Bach

copyright ©TestingTimes 2013

SIMULTANEOUS

Learning

Design

Execution

copyright ©TestingTimes 2013

Activities

EXPLORATORY TESTING

Modelling

Decision Making

Configuration

Operation

Observation

Evaluation

Learning

Testing

Design

Strategy

copyright ©TestingTimes 2013

TESTER CENTRIC

DesignTesting

Learning

AutodidacticSelf Awareness

AutonomyResponsibility

Courage

copyright ©TestingTimes 2013

MYTH #1

Exploratory Testing is unstructured

copyright ©TestingTimes 2013

PROBLEM SOLVING STRATEGIES

copyright ©TestingTimes 2013

• Explicit

• Repeatable

• Context less important

• Knowledge but not skill

ALGORITHMS

copyright ©TestingTimes 2013

Heuristics

A heuristic is a fallible method of solving a problem or making a decision.

• Requires Skill

• Context Dependent

• Less Visible

PROBLEM SOLVING STRATEGIES

The essence of heuristics: http://www.satisfice.com/blog/archives/462

copyright ©TestingTimes 2013

EXPLORATORY TESTING HEURISTICS

• FEW HICCUPS (Ways to Recognise Bugs) - Michael Bolton

• SFDIPOT (Ways to Model and generate test ideas) - James Bach

• Heuristic Test Strategy Model - James Bach

• http://www.qualityperspectives.ca/resources_mnemonics.html

copyright ©TestingTimes 2013

MYTH #2

You can’t use documents in Exploratory Testing

copyright ©TestingTimes 2013

IS DOCUMENT A DIRTY WORD IN EXPLORATORY

TESTING?

copyright ©TestingTimes 2013

Documents are great for?

Reflective Tool

Keeping Track of what we do

Sharing Information with Others

copyright ©TestingTimes 2013

REPORTING

• Bug Reports

• Test Reports

• Mind Maps

• Wiki

• Conversations

• MiPs

• Charters and SBTM

copyright ©TestingTimes 2013

copyright ©TestingTimes 2013

J Bach

copyright ©TestingTimes 2013

SBTM

• Session is the basic testing work unit

• Each session is chartered

• ~ 90 minutes

• Debrief

Read about it here: http://www.satisfice.com/sbtm/

copyright ©TestingTimes 2013

SESSION SHEET FORMAT• Session charter (includes a mission statement, and

areas to be tested)

• Tester name(s)

• Date and time started

• Task breakdown

• Data files

• Test notes

• Issues

copyright ©TestingTimes 2013

What value

am I offering by

documenting this?

copyright ©TestingTimes 2013

• Challenge Documentation

•On the Light side

• Begin by Thinking, then read

•Where possible, speak

• End by date ? (best before date)

• Byproducts not end results (its not an end its a means)

COBWEB

copyright ©TestingTimes 2013

QUESTIONS?

copyright ©TestingTimes 2013

THANK YOU!

amcharrett@testingtimes.com.au@charrett

Skype: charretts

Recommended