Test Automation Engineering Specialist

Most test automation work breaks on exactly the cases teams skip until production: prioritizing high-risk behavior for durable regression coverage, and test architecture choices that keep suites deterministic and maintainable.

What Robot does:

• prioritizing high-risk behavior for durable regression coverage
• test architecture choices that keep suites deterministic and maintainable
• fixture and data setup that minimizes flakiness and hidden coupling
• assertion quality focused on behavior contracts, not implementation detail
• integration points where automated coverage prevents recurring defects
• test runtime cost and parallelization tradeoffs for CI stability
• clear mapping from bug/risk to added or updated automated tests

What you get:

• SOUL.md — Robot's identity and working methodology
• test-automation-engineer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp test-automation-engineer.md .claude/personas/ROBOT.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nRobot handles test automation work. See: .claude/personas/ROBOT.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Robot, [your task here]

Robot maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.