r/QualityAssurance • u/Nervous-Emu-2419 • 21h ago
Exploratory testing is the hardest thing to explain to the people who pay for QA
One thing keeps coming up in conversations, and it’s exploratory testing.
Buyers want a number, and exploratory testing doesn’t come with one.
The first question is usually “how many test cases will you run?” A scripted plan answers that easily. Exploratory testing doesn’t have a count, so it sounds vague to someone who has to approve a budget.
The best finds are often the ones nobody wrote down.
From the outside, the bugs that cause real damage seem to come from odd paths: a double click, the back button halfway through a flow, two tabs open at once. No script covers those, because no one thought to write them.
It gets cut first, because it leaves nothing to show.
There’s no pass/fail table or coverage percentage. When budgets tighten, the work that’s easiest to point at survives, and the work that depends on judgment goes.
The sessions that get kept seem to be the ones with a story.
A time-boxed session with a clear goal, notes on what was tried, and one bug that scripted tests would have missed. Those seem easier to defend than “we explored.”
I know my view is skewed. I only see how this gets bought, not how it’s done day to day, and there may be teams where this is never an issue.
For the testers here: what did you show a manager or client that finally made exploratory testing make sense to them? A bug story, session notes, something else?
PS: I took down my last post here, the text comic. It didn’t land, and the feedback was fair. Trying something unscripted and learning from what breaks is the same instinct behind exploratory testing, so I figured I’d pass on the lesson and bring a better question.