Key Takeaways
AI agent testing is rapidly professionalizing. What was once manual, exploratory experimentation is now being replaced by repeatable frameworks, structured evaluation lifecycles, and automated security testing. Tools from Promptfoo, Databricks, and Playwright all point to the same conclusion: high-quality AI systems require disciplined inputs, explicit standards, and measurable outputs—just like traditional software.
Read Today’s Notes
Welcome back to the AI in Testing Coach podcast.
Today’s episode is all about one big shift happening right now in QA:
AI agent testing is moving from improvisation to engineering discipline.
We’re going to cover four major developments that, taken together, show how fast this space is maturing.
First, let’s start with Databricks.
Databricks has published a comprehensive best-practices framework for evaluating AI agents across their entire lifecycle. What’s important here is not just the tools they mention—but the mindset they promote.
They recommend starting with offline evaluation using surprisingly small datasets—sometimes as few as 10 to 20 carefully designed test cases. From there, teams move into more structured evaluations and eventually into production monitoring, tracking metrics like accuracy, safety, latency, and cost.
For QA teams struggling with the question, “How do we define ‘good enough’ for an AI agent?”—this framework provides a practical, structured answer.
Next, let’s talk about Promptfoo.
One of the hardest things to test today is a stateful, multi-step AI agent, especially those built using LangGraph. Promptfoo directly addresses this with a full, end-to-end tutorial for testing LangGraph agents.
What stands out is how accessible this is for testers.
With a single command—npx promptfoo@latest init --example langgraph—
you can scaffold an entire agent testing project.
Test cases are written in YAML, not code, which dramatically lowers the barrier to entry. Even more importantly, Promptfoo includes built-in red teaming, automatically scanning for prompt injection vulnerabilities—currently the number one risk on the OWASP LLM Top 10.
Results are visualized in a clean web dashboard, making failures easy to understand and communicate.
That brings us to security.
A new open-source tool called ZeroLeaks focuses exclusively on prompt injection scanning. You point it at your AI assistant, and it runs a suite of known attack patterns designed to extract system prompts or bypass guardrails.
The key takeaway here is this:
LLM security testing is no longer specialized or optional.
It’s becoming a standard, automatable step in the QA workflow.
Finally, let’s look at Playwright Labs.
They’ve introduced an interesting idea: packaging testing best practices as reusable “skills” that can be fed into AI coding assistants like Copilot, Claude, or Cursor.
Instead of hoping your AI generates good Playwright tests, you guide it with ranked, structured best practices. The result is more consistent, maintainable, and standards-compliant test code.
This reinforces a theme we keep seeing:
AI works best when structure is provided up front, not when it’s left to guess.
The Big Picture
Here’s what all of this tells us.
Structure is becoming the defining factor of AI quality in QA.
- Playwright Labs adds structure to AI code generation
- Promptfoo adds structure to agent testing and red teaming
- Databricks adds structure to evaluation and production monitoring
Together, they signal that AI agent testing is no longer experimental. It’s becoming a formal QA discipline with frameworks, tools, and shared standards.
Actionable Tip of the Day
If you’re testing or building AI agents, do this one thing this week:
Install Promptfoo and scaffold your first LangGraph test project using the example template. Start with just five core test cases—and then immediately run the built-in red team scan.
That single step will put you ahead of most teams currently shipping AI to production.
That’s it for today’s AI Testing & Tech Daily Brief.
If you found this useful, subscribe and we’ll continue tracking how AI testing becomes a core QA competency in 2026.
Companion Newsletter
Structure Is the Difference Between AI Demos and AI Quality
As AI systems evolve into agents that reason, act, and persist state, testers face a familiar problem: complexity without structure leads to unreliable results.
This week’s signals point to a clear trend. Whether it’s Databricks defining a lifecycle for agent evaluation, Promptfoo standardizing LangGraph testing, or Playwright Labs constraining AI code generation with explicit “skills,” the message is the same: AI quality improves when testers impose structure.
Security is following the same path. Prompt injection testing is no longer a manual, niche exercise. Tools like ZeroLeaks and Promptfoo’s built-in red teaming make automated LLM security testing a baseline expectation, not an advanced specialty.
A practical place to start today:
- Scaffold a small agent test project
- Write a handful of core behavioral tests
- Run automated prompt injection scans
- Observe consistency across runs
This is how AI testing shifts from experimentation to engineering.
Research & References
- Databricks: Agent Evaluation Framework
https://www.databricks.com/glossary/agent-evaluation
- Promptfoo: Testing Stateful LangGraph Agents
https://www.promptfoo.dev/docs/guides/evaluate-langgraph/
- ZeroLeaks: Prompt Injection Scanner
https://github.com/ZeroLeaks/zeroleaks
- Playwright Labs: Best Practices as Code
https://dev.to/vitalicset/introducing-playwright-labs-best-practices-as-code-198n
- OWASP Top 10 for LLM Applications
https://owasp.org/www-project-top-10-for-large-language-model-applications/
- LangGraph Documentation
https://langchain-ai.github.io/langgraph/
- garak: LLM Vulnerability Scanner
https://github.com/leondz/garak
