Exploratory Testing takes software testing skill. It also requires the tester be courageous. Let me explain.
Exploratory testing is an approach, not a technique. Exploratory Testing is simultaneous learning, design and execution. What information we learn about a product, helps dictate our tests providing us with information that we can share with people around us.
Exploratory Testing is tester centric, meaning the tester is central to the testing taking place. The tester has the autonomy and the responsibility to make decisions about what to test, how to test, how much to test and when to stop. This may seem blatantly obvious to some, but its surprising the number of test teams where this is not the case.
It’s all powerful stuff, generating an environment where the tester must constantly reflect upon the changing project and product environments, enabling the tester to be engaged and mindful as they test.
I honestly can’t think of a better approach to software testing.
But there is a catch. Exploratory Testing also demands great courage.
When you start to take responsibility for your testing it’s not done in isolation. Testing requires interaction with many different people such as developers, project managers, scrum masters, product owners, customer support and business people. We share information that’s not always good news. It’s in the form of bugs found and the possible impact of this information on the business. The resulting consequences of the information we share often leads to delays in releasing, changes in workload, context switching and revising strategies.
In scripted testing, testers have artefacts which they measure and count giving an illusion of certainty but really this is smoke and mirror reporting and generally offers little genuine information. “We have reached 78% test coverage, with a DDR of 85%”
Exploratory Testing doesn’t have ‘dutch courage’ to rely on. It requires us to have conversations about our information in potentially hostile environments. Sometimes we can feel like the lone fish swimming against the tide of the silent majority. It can be tough and as testers, we need to learn to develop how to speak about our testing, how to tell a story (James Bach and Michael Bolton have both written on this).
Here’s a list of ways that have helped a quaking knock-kneed tester like myself discover her backbone:
Speak to someone you trust about your concern. Vocalising a fear helps to make it tangible and sometimes gives strength when you discover its a shared concern.
Be coached or mentored on how to speak about testing with confidence
Take small steps. Speak to people sympathetic to your cause, sound out ideas. See if other people can help.
Try not to lose faith, be persistent. Keep your eyes on the goal, even if sometimes you fail to speak out.
Emotions are your toolbox. Anger and frustration can be very useful emotions! Use your emotion to give you the courage to speak out. (I learned that at PSL this year..thanks to Jerry, Johanna & Esther)
Sometimes you need help. Be humble enough to know that sometimes change is out of your capabilities. See if you can find help through the testing community or see if you can bring someone in to help affect the change.
But mostly, it’s about practice. Courage breeds courage. Standing up to little things helps give you the courage to stand up to greater things in the future. Be brave. Be strong.
What drives me most of all is that I want to be able to walk away from a situation with my head held high in the knowledge that I may not have changed the world, but I’ve had my say.
Now that’s a good days work.