Our AMA sessions are open-floor by design — no slides, no agenda, just a room (or a call) where anyone can ask anything about applying AI to testing. A pattern has emerged in what people actually want to know.
"Will this replace my job?"
No — but it will change what your job looks like. The testers who struggle are the ones treating AI output as final. The ones who thrive treat it as a fast first draft that still needs their judgment.
"How do we stop AI from generating tests that pass but don't test anything real?"
This is the single most common technical question we get, and it's a good one. The fix isn't a smarter prompt — it's a review step baked into your process, the same way you'd review a junior engineer's pull request. We cover this in depth in our workshops.
"What tools should we actually use?"
We deliberately don't lead with tools, because the tool landscape changes every few months and the underlying skill — knowing how to direct, review, and integrate AI into a testing workflow — doesn't. Pick tools that fit your existing stack, not the other way around.
"Where do we even start?"
Almost always: with an assessment of where your current process actually stands, not where you assume it stands. That's the most common first engagement we run with new clients, for exactly this reason.
Got a question that's not here? Bring it to the next AMA — that's what it's for.
Want help putting this into practice?