When to Use AI Agents vs Scripts
In practice, most teams use a combination: AI agents for exploration and edge cases, scripts for critical deterministic flows, and manual QA for subjective evaluation (design, UX, brand consistency).
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
When to use AI agents, scripts, and manual QA.
| Scenario | AI Agents | Scripts | Manual QA |
|---|---|---|---|
| Exploratory testing | ✅ Best - discovers edge cases through varied behavior | ❌ Fixed paths only | ✅ Good - but slow and expensive |
| Regression testing | ✅ Good - handles UI changes gracefully | ✅ Best - fastest execution | ❌ Too repetitive |
| Exact same steps every time | ⚠️ Possible but overkill | ✅ Best - fully deterministic | ❌ Error-prone over time |
| Testing multiple user flows | ✅ Best - tries different approaches automatically | ⚠️ Need separate script per variant | ✅ Good - but doesn’t scale |
| Complex calculations | ❌ Use assertions in code instead | ✅ Best - precise math | ⚠️ Manual calculation prone to errors |
| Form filling with realistic data | ✅ Best - understands context | ⚠️ Need hardcoded test data | ✅ Good - but tedious |
| Testing preview environments | ✅ Best - automatic PR reviews | ⚠️ Need CI/CD integration | ❌ Requires manual coordination |
| First-time test coverage | ✅ Best - AI Chat Assistant sets up quickly | ❌ Requires upfront investment | ⚠️ Slow to establish baseline |
Was this page helpful?