Playwright Test Prompt
getByRole over CSS chains, auto-wait over sleep, web-first assertions — Playwright tests written the way Playwright wants.
View Resource →Test Case Prompt Generator resources
Build test generation prompts — unit, integration, or E2E — with framework modes and edge-case coverage rules.
Unit Test Prompt — Isolation Done Right
Mock the dependencies, test the business logic, one behavior per test — the unit testing contract that bans plumbing tests.
View Resource →API Test Prompt — the Contract Is the Subject
Status codes, response shapes, 401 vs 403, idempotency — API tests that test the contract, not the implementation.
View Resource →Authentication Test Prompt
Login, token refresh, and everything that must fail: expired tokens, wrong permissions, malicious credentials — auth tested as behavior.
View Resource →E2E Test Prompt — User Journeys, Not Functions
Cart to confirmation as a user would do it — with the failure scenarios real users actually trigger: refreshes, back buttons, double clicks.
View Resource →Edge Case Test Prompt — Hunt the Boundaries
Null, empty, min, max, off-by-one, malformed, unicode — the systematic boundary hunt that finds bugs where they actually live.
View Resource →Integration Test Prompt — the Boundary Is the Subject
Real database, real services, real transactions — integration tests that verify round-trips and rollback, not mocked theater.
View Resource →Regression Test Prompt — Pin It Before You Change It
Characterization tests for legacy code: assert what it does TODAY — bugs and all — so tomorrow's change can't lie about its impact.
View Resource →Selenium Test Prompt
Explicit waits, stale-element handling, drivers that actually quit — Selenium regression tests that hold the legacy fort.
View Resource →Validation Test Prompt
Required fields one at a time, invalid formats, business rules at their exact boundaries — validation tested the way users break it.
View Resource →