Skip to main content

Automation tester playbook

The automation tester directs agents to generate and maintain automation rather than hand-writing it — and owns the health of the suite the whole pipeline depends on.

The work​

  • Framework & pattern standards per the radar — Screenplay / Page Object, selected and shared.
  • Selector & wait-strategy rules agents must follow — the difference between a stable suite and a flaky one.
  • CI wiring — automation runs in the pipeline, gating the merge gate.
  • Suite-health ownership — flake rate, runtime, and coverage of critical journeys are this role's metrics (flaky-test policy).

Directing, not typing​

At agent speed, hand-writing every test is the bottleneck. The automation tester specifies what to test and the patterns to follow, directs agents to generate it, and reviews for honesty (AI-generated-test review). Their leverage is in the harness and the standards, not in typing test code.