162 / 168 · 01 Agent Skills for Browser Automation · Future Directions: Where AI-Driven Testing Is Heading← prev⊞ allnext →☰ Read as one page
22.7What This Means for Your Career
Skills to Develop
- AI agent architectures — ReAct patterns, multi-agent systems, tool use
- Testing AI systems themselves — LLM evals (Ragas, TruLens, OpenAI Evals), RAG metrics, MCP/A2A flow testing; this is now explicit in QA job postings
- Prompt/plan engineering for testing — writing effective specs and skill files
- WebDriver BiDi protocol — the technical standard underneath
- Token economics — understanding and optimizing AI costs as a first-class quality metric
- CI/CD for AI workflows — running agent-driven tests in pipelines, reviewing healer patches
Skills That Are Declining
- Manual selector management — refs, intents, and AI locators replaced it
- Explicit wait strategies — actionability checks handle this
- Page Object boilerplate — plans + seed tests replace class hierarchies
- Browser-specific workarounds — BiDi standardization eliminates these
The QA Engineer of 2028
Instead of writing and maintaining test scripts, you'll:
- Define testing intent in natural language
- Curate AI-generated test suites and review healer patches
- Design evals for the AI features your product ships
- Manage AI test infrastructure costs
- Design test strategies that agents can execute
- Interpret AI-generated failure analysis
The job title might change from "QA Automation Engineer" to "AI Test Architect" or "Test Intelligence Engineer."