How to Stay Irreplaceable When Agents Write Your Tests with Jonathon Wright
Categories: Podcasts , Test Guild
AI is revolutionizing software testing by automating tasks and enabling intent-driven, model-based approaches, but human oversight remains crucial due to AI’s limitations in critical thinking and context understanding. Testers must navigate challenges like noise from AI agents and ensure reliability while leveraging their expertise to validate requirements and deliver real value.
Test Guild
Test Guild - hosted by Joe Colantonio has main topic focus on Testing or Automating. Each episode has a different guest. Show notes have comprehensive links and usually a full transcript. Released as audio and video.
- https://testguild.com/
- https://testguild.com/podcasts/automation/
- https://www.youtube.com/playlist?list=PL9AgRtJkydU1jqvx46esyr56BXtm1QEds
- https://www.youtube.com/@JoeColantonio
Episode Details
- Show Notes: https://testtalks.libsyn.com/how-to-stay-irreplaceable-when-agents-write-your-tests-with-jonathon-wright
- Published: 2026-09-15T16:26:00Z
- Duration: 34:04
- Author: Unknown
Overview
The podcast discusses the evolving role of AI in software testing, emphasizing how advancements in agentic systems and large language models (LLMs) are transforming traditional practices. While AI can automate repetitive tasks like browser testing or generate code at scale, it struggles with non-deterministic behaviors, context understanding, and critical thinking - highlighting the ongoing need for human oversight. The discussion critiques the overreliance on LLMs, noting they represent only a small part of AI and are often misapplied, leading to inefficiencies rather than solutions.
A key theme is the shift from manual scripting and regression-based testing to intent-driven, model-based approaches powered by neuro-symbolic languages and AI agents. Tools like OpenWrite and platforms enabling cross-framework automation support this transition, allowing testers to focus on higher-level design and verification. However, challenges remain, including managing noise from poorly implemented AI agents, ensuring test reliability through confidence engineering, and validating requirements early in development. Ultimately, testers are positioned as essential contributors who bring domain expertise, ask critical questions, and ensure AI systems deliver real value - not just automation for its own sake.
What If
-
What if you trained an AI agent to handle your repetitive testing tasks and then measured its output like a manager?
-
Move: Identify one recurring, time-consuming test task (e.g., regression smoke tests on a web app), document your process step-by-step, then use a tool like Cursor or GitHub Copilot to generate a script that simulates your actions. Deploy it as an autonomous agent using a framework like ZapTest or OpenWrite to run weekly.
-
Why Now?: Browser automation can now be generated in under 30 seconds with AI, and agentic systems are stable enough to run unattended - waiting means falling behind solo developers who offload labor while they focus on high-leverage work.
-
Expected Upside: Free up 5 - 10 hours/month for strategic work (e.g., exploratory testing, security checks), reduce burnout from rote tasks, and gain firsthand insight into managing AI agents before scaling to more complex workflows.
-
-
What if you shifted left by validating product ideas with AI-generated test scenarios before writing any code?
-
Move: Take a new feature idea (even a sketch in Figma or a bullet list) and prompt an LLM to generate 20 edge-case test scenarios based on regulatory, accessibility, or usability risks (e.g., WCAG compliance, data drift). Use these to challenge assumptions and refine requirements before development begins.
-
Why Now?: With AI generating code faster than ever, the bottleneck has moved to design and intent validation - teams that verify requirements early avoid costly rework, especially as confidence engineering becomes critical in AI-driven development.
-
Expected Upside: Reduce wasted effort by catching flawed assumptions early, improve collaboration with stakeholders by surfacing hidden risks, and position yourself as a value-driven developer who prevents problems instead of just fixing them.
-
-
What if you built a personal “verification blueprint” to guide AI agents and increase their signal-to-noise ratio?
-
Move: Create a living document (in Markdown or Notion) that defines your core quality criteria - e.g., performance thresholds, accessibility rules, security guardrails - and integrate it into your AI agent prompts via RAG (retrieval-augmented generation). Use it to evaluate every agent-generated test report or code change.
-
Why Now?: Most teams using 50+ AI agents see diminishing returns due to noise; solo operators who curate focused, personalized verification standards will get reliable results where others fail, aligning with the shift toward confidence engineering.
-
Expected Upside: Increase trust in AI outputs, reduce manual review time by filtering out irrelevant or low-quality agent suggestions, and create a reusable asset that compounds value across projects and clients.
-
Takeaway
-
Adopt intent-based testing by using tools like OneScript or ZapTest Enterprise to define high-level test goals (e.g., “test all of Joe’s website”) instead of writing detailed scripts, reducing development time and increasing coverage.
-
Implement confidence engineering practices by creating verification blueprints that guide AI agents, ensuring test reliability and traceability, especially when validating AI-generated code at scale.
-
Migrate existing test automation scripts across frameworks efficiently using OpenWrite, avoiding vendor lock-in and enabling seamless transitions between tools like Selenium, Appium, or Robot Framework.
-
Shift testing left by validating requirements and designs early using DesignOps - integrate testing from Figma prototypes before coding begins - to prevent wasted effort on flawed implementations.
-
Focus on domain-specific expertise in accessibility, security, and compliance (e.g., WCAT, VPAT) to enhance AI agent outputs, positioning yourself as a human overseer who adds value through critical evaluation and context.
For a PDF of longer Software Testing Podcast Episode Summaries with Briefing Notes and more detailed summary notes, visit EvilTester Patreon Podcast Summaries.