| name | qa-playwright-e2e |
| description | Use when planning, adding, or reviewing browser QA, Playwright coverage, visual smoke checks, or ERTZU end-to-end marketplace scenarios. |
QA Playwright E2E
When To Use
Use this skill for QA strategy, browser smoke testing, future Playwright setup, visual checks, and end-to-end flow coverage. The repo currently has no Playwright config or app-level test runner.
ERTZU-Specific Instructions
- Do not install Playwright or any test package without explicit approval.
- If tests are added, update
docs/ai/QUALITY_GATES.md and package scripts.
- Prioritize high-risk marketplace, auth, admin, and payment flows.
- Use a local dev server only after confirming the available script.
Files And Areas To Inspect
package.jsondocs/ai/QUALITY_GATES.mdsrc/app/listings/page.tsxsrc/app/listings/[id]/page.tsxsrc/app/sell/page.tsxsrc/app/buy/page.tsxsrc/app/bid/checkout/page.tsxsrc/app/checkout/[id]/page.tsxsrc/app/notifications/page.tsxsrc/app/admin/page.tsxsrc/app/login/page.tsxsrc/app/signup/page.tsx
Concrete Checks
- Verify
npm run lint and npm run build after code changes when feasible.
- For future E2E coverage, define smoke tests for product grid, product detail, login redirect, ask creation, bid placement, buy-now, checkout status, notifications, and admin guard.
- Include mobile and desktop viewport checks for marketplace and checkout pages.
- Include visual checks for product image visibility, CTA hierarchy, text overflow, and loading/error states.
- Include negative checks for unauthenticated access, self-bid/self-buy, blocked users, and non-admin admin access.
- Keep payment tests in mock or test mode unless explicit live credentials and approval exist.
Mistakes To Avoid
- Do not invent a
test command.
- Do not install browser tooling without approval.
- Do not run production-impacting payment or database tests.
- Do not leave QA docs saying tests exist when only manual checks exist.
- Do not rely on screenshots alone for auth/payment permission coverage.
