Structured Exploratory Testing Strategies That Work - Callum Akehurst-Ryan

Using Exploratory Testing to Uncover Risks and Unknowns in Software Projects

🚨 Are we actually testing too much sometimes? Just because we run a lot of tests doesn’t mean we’ll find a lot of bugs. Here’s how we can solve this: Free Online Workshop

"We do exploratory testing when things are unknown. But from the unknown, we get information. That makes things known." - Callum Akehurst-Ryan

In this episode, I talk with Callum Akehurst-Ryan, a quality coach with nearly 20 years of experience, about why exploratory testing is far more than random button-pushing—and how teams waste it by using it in all the wrong places. Callum walks us through practical exploratory testing techniques that help uncover risks in non-functional requirements like performance and security, especially when no one has bothered to document what "good" should look like. We discuss how to structure exploration with timeboxes and risk-based scopes, when to turn findings into automated tests, and why retrofitting quality into existing systems demands a different software testing strategy than most teams realize.

Callum Akehurst-Ryan (he/him) is a testing specialist and quality coach with over 17 years of experience across a range of different industries and development methodologies. With a focus on holistic quality engineering and exploratory testing, Callum teaches others in core and agile testing concepts. He’s also a kick-ass dungeon master!

Highlights:

• Exploratory testing finds information about unknowns, not pass/fail confirmation of known requirements.
• Scope exploration by risk and timebox sessions to avoid endless testing rabbit holes.
• Document what matters: defects, conversations, knowledge—not exhaustive test evidence in unregulated contexts.
• Turn exploratory findings into automated regression tests; exploration isn't meant for repeatability.
• AI tools can spider websites to document workflows, enabling golden master testing retroactively.