Trigger diagnostic

Playwright tests should give release signal, not roulette.

If retries, timing fixes, and locator rewrites keep returning, the problem is usually architecture, data control, isolation, or CI behavior. This diagnostic finds the smallest credible path back to trust.

What gets inspected

Failure patterns, not random test cleanup.

The review looks at fixture design, data setup, waits, browser context isolation, network dependencies, CI runners, retries, trace evidence, and ownership rules.

Output

A ranked list of root causes and the first fixes most likely to improve release signal.

Evidence needed

CI history, traces, reports, representative failures, framework structure, and release-gate rules.

Not a fit

Teams with no automation yet, or teams only looking for bulk test writing capacity.

Email RahulBook diagnosis