Menu

Ask the agent for a Playwright assertion, not another manual QA checklist
📰

Ask the agent for a Playwright assertion, not another manual QA checklist

DEV Community: frontend·Sherotree·9 days ago
#PE3PcGhS
#devtofrontend#devto#dev#assertion#checklist
Reading 0:00
15s threshold

After a UI PR, agents (and humans) love dumping a fresh “manual QA checklist” into the description: click here, hover there, check mobile, verify empty state. Those bullets rot by the next sprint. Nobody re-runs them. Regressions still ship.

I’ve started asking for something sharper: one Playwright assertion (or whatever E2E runner the repo already uses) that fails without the fix and passes with it. Same interaction. Same locator style. No new checklist theater.

What “one assertion” means here

Cover the changed flow only — one interaction, not the whole suite

Reuse existing test helpers / page objects / fixtures

Fail without the fix; pass with it (prove it once locally or in CI)

Match the locator strategy already in the folder ( getByRole , data-testid, whatever neighbors use)

Land in the same PR as the UI change

If the agent can’t point at an existing helper, that’s a signal the flow isn’t tested yet — still better than a checklist you’ll never open again.

Prompt shape that gets a real assert

Add…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.