Why We Do Exploratory Testing Diagram By Simon Tomes — Tentamen Software Testing Blog

credit: https://www.ministryoftesting.com/dojo

TL;DR

Now that we know James Bach’s idea of the Thread-Based Test Management, let’s explore the first of three digestible diagrams created by Simon Thomes Start with the Why. This is a part of the Exploratory Testing Pathway. Many thanks to Marcel who sublimed this great resource on his blog, That’s the buffet table.

Simon Tomes

I had a privilege to meet in person Simon at Test Bash Brighton 2017 open session about his testbuddy.co application for exploratory testing. It was a great 45-minute discussion about exploratory testing application feature set. Three years after, the test buddy is ready to use product.

Simon is not only an exploratory testing advocate but also a skillful exploratory testing practitioner. Three Digestible Diagrams to Describe Exploratory Testing is an excellent example of that fact.

What Is Not Exploratory Testing

As we already wrote on our blog, exploratory testing is not ad hoc testing, some kind of a play with an application under test. Simon nicely summarizes in the following diagram what is not exploratory testing:

credit: https://www.ministryoftesting.com/dojo

We need to stress two essential aspects of this diagram:

  • ad hoc testing is when we do not have an idea of why we test. Charter is what we have in exploratory testing for general test strategy
  • when we only hunt for bugs means that we are at the second level of the Beizer testing organization. We usually find many, not critical bugs that just annoy the whole team.

Start With The Why

And continue with the how and what. When you can explain why, how, and what you are testing with exploratory testing, you would prove and move from bug hunting and ad hoc testing paradigm.

We need to stress Simon’s following points:

  • exploration is unscripted (no steps but with charter and area) but documented activity (session testing notes.)
  • Share with the team discovered information (not only bugs).
  • Exploratory testing is a continuous activity, which means that valuable testing is never done.

Originally published at https://blog.tentamen.eu on September 2, 2020.

Founder of Tentamen, software testing agency.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

CS373 Fall 2021: Mark Grubbs : Final Entry

What Makes a Good DevOps Engineer?

Hand showing peace sign

CakePHP 4 Google Bar Chart Integration Tutorial

What’s New in RDFox Version 5.4: The Console Update?

6 Ways to Prepare for Your Spouse’s Deployment

How to Install the Universal Render Pipeline

Patterns for Continuous Integration with Docker on Travis CI

SRE / DevOps / Kubernetes Weekly Collection#41(Week 46)

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Karlo Smid

Karlo Smid

Founder of Tentamen, software testing agency.

More from Medium

Critics and confusion about testing

DevOps vs Agile — Understand The Difference!

The Eternal Wait — Missed Testing a Persona?

The Future of Software Testing — Top 4 Cloud Testing Trends in 2022