generate
SolidGenerate Playwright tests. Use when user says "write tests", "generate tests", "add tests for", "test this component", "e2e test", "create test for", "test this page", or "test this feature".
Install
Quality Score: 83/100
Skill Content
Details
- Author
- adriannoes
- Repository
- adriannoes/awesome-agentic-ai
- Created
- 11 months ago
- Last Updated
- 1 weeks ago
- Language
- Jupyter Notebook
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
playwright-test-generator
Use this skill to generate new Playwright end-to-end tests from scratch — for a page, a user flow, a form, or a component — taking them from zero to reviewed, passing specs. Reach for it whenever someone wants to add, write, create, or scaffold Playwright E2E coverage, fill coverage gaps for uncovered routes, or bootstrap the first e2e test for a project and set up its conventions. It explores live pages only on local/disposable or externally isolated approved non-production targets to discover real selectors, proposes a scenario plan for approval, generates Page Object or flat specs that match the existing project style, then runs an e2e review and the suite before handing back. Do not use it for debugging an existing failing Playwright test (use playwright-debugger), reviewing or auditing tests that already pass (use e2e-reviewer), generating Cypress tests, or writing unit, component, or integration tests with Jest, Vitest, or Testing Library.
generate
Write automated tests from a test design or a described behaviour, in whatever stack the project uses. Use when asked to generate, write or add tests, to automate a design, or to cover a new feature with tests.
playwright-tester
Author persistent Playwright .spec.ts tests, run them natively with `npx playwright test` (zero AI tokens per run), and fix failures in a diagnose-first loop. Use whenever the user wants to test a web app, check whether a frontend works, run or re-run UI tests, verify a form or login flow, do end-to-end testing, reproduce a UI bug, smoke test a site, catch a visual regression, check for broken links, test across browsers, add regression coverage, audit every component, sweep a codebase for UI bugs, or confirm recent changes did not break anything. Also triggers on "run my e2e tests", "my playwright tests are failing", "check the app in a browser", "does this page still work after my change", "test the happy path", "write e2e tests", "set up playwright", "find UI bugs", or "test the whole app and tell me what is broken". Prefer this over driving a browser live or screenshot-based checking for anything that should be verifiable more than once.