Nothing to hand? Load the
— fixed sleeps, brittle selectors, a UI login before every test, a force-click, an
assertion-free test and a leftover test.only — or the
,
where the correct verdict is merge-ready and the useful output is what to add next.
Paste the tests — the prescan is free
No upload, no AI: the prescan reads your source in the browser and lists what it mechanically found. The test and suite inventory, then the flags — fixed sleeps (waitForTimeout, numeric cy.wait), networkidle waits, brittle selectors (nth-child, XPath, class chains), { force: true }, tests with no assertions, if (isVisible()) branching, Playwright calls without await, shared module-scope state and .serial mode, hardcoded absolute URLs, UI login repeated in beforeEach, a leftover .only, and secret-looking literals. Each group explains why it matters. This part costs nothing and happens while you type.
The AI reviews them — this is the metered part
A senior test-infrastructure engineer's pass: a suite-trustworthiness posture with the single most important change named, the inventory with each construct's role, and prioritized findings across flakiness, correctness, isolation, maintainability, performance and hygiene — each with the problem, the concrete impact on CI and the team, the fix and a corrected TS/JS fragment. Every prescan flag is confirmed or explicitly set aside. Findings may only cite tests, suites, hooks and selectors that actually appear in your code. Pricing is honest: a worst-case amount is reserved before the run and only what the run actually uses is charged — the meter next to the button shows both.
Fix, export, re-run
Every corrected snippet in one paste-ready block, the findings as GitHub PR review comments with ```suggestion fences you can apply from the review UI, a tickable action checklist for the ticket, the findings table as CSV, and Markdown or JSON export of the whole review. Then start fixing: the prescan re-runs as you edit and the strip above the run button counts the flags you have cleared, the ones still open and any you have just introduced — in the browser, for free, before you pay for a second review. Reviews are saved to your SkillSafe account when you are signed in, so they follow you to another machine; restore puts the code back in the form too.
Derived from the @wshobson/e2e-testing-patterns skill (MIT license).