If your exploratory testing uncovers an area that may be an ideal candidate for automation, what steps would you go about communicating that to the developers/automators to get it done?
16 Mar 2026
Create Moment
In this moment:
Gary Hawkes
Great question from Gary Hawkes.
If your exploratory testing uncovers an area that may be an ideal candidate for automation, what steps would you go about communicating that to the developers/automators to get it done?
I'd aim to answer the following questions:
- What was it in particular about the exploratory testing that uncovered a good candidate for automation? What makes it an ideal candidate?
- Was there a particular risk that was addressed during the exploratory testing? Do we need to repeatedly check for this risk? And could automation repeatedly check for this risk?
- What new information revealed itself during the exploratory testing that is related to automation?
- When did the exploratory testing uncover information about existing features and new features? Does time and effort have an influence on what should or shouldn't be automated?
- How maintainable would the automation be for this ideal candidate?
- Who do I want to communicate with? What are their goals and motivations? How lined up are we as a team when it comes to quality?
- What resistance might I meet about my suggestions? How might I handle any objections?
- What trade offs are we making to not automate something we discovered during exploratory testing?
- What ally or buddy can I lightly mention this ideal candidate to? Who can I sense check with first before putting forward a formal case?
- What timely process can we put in place if this area were to be automated? How can we continue to make sure the automation of this area is valuable?
Answering those questions would then inform my communication approach.
There's also another lens worth considering. Should exploratory testing efforts inform automation efforts? Sometimes I don't think they should. Exploratory testing is powerful when it doesn't have automation in mind. During an exploratory testing session folks might be thinking, "I wonder if this would be a good candidate for automation?" This is a distraction. The real goal of exploratory testing is a technique and way of thinking that aims to reveal helpful information about risks. And that information helps teams make important decisions, regardless of automation or not.
Having said that, automation done well is also another technique for revealing helpful information about risks. So it's clear how they are connected. I guess there's also the argument that automation frees up time to run exploratory testing sessions. I think there are some flaws in that argument yet in some cases it runs true.
I hope this helps, Gary. Thanks again for your question.
Let me know if you'd like me to elaborate on any of this.
See more questions and answers in the AMA about Exploratory Testing collection.
Simon Tomes
Community Lead at Ministry of Testing
he/him
Hello, I'm Simon. Since 2003 I've had various roles in testing, tech leadership and coaching. I believe in the power of collaboration, creativity and community. 🎓 MoT-STEC qualified.
Sign in
to comment
Better than a generic video, see YOUR test, live, ready to show you what matters most: quality at scale.
Explore MoT
Tue, 17 Mar
Thunders Connect – Mar 17, Station F, Paris: QA & testing future, certification, product updates, panel, Station F tour & first-ever Thunders Awards. RSVP if in Paris!
Ascend to leadership roles by mastering strategic skills in automation strategy creation, planning and execution
Into the MoTaverse is a podcast by Ministry of Testing, hosted by Rosie Sherry, exploring the people, insights, and systems shaping quality in modern software teams.