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.
pw-test-generator
Generates a Playwright test spec — JavaScript or TypeScript, matched to the target project's existing conventions — from a described user flow or scenario. Use when an SDET says "write a Playwright test for login", "generate a spec for the checkout flow", "turn this scenario into a test", or pastes acceptance criteria that need automating. Detects the project's language and conventions, reuses existing fixtures/page objects, and produces a runnable draft using semantic locators and web-first assertions — the engineer still runs it.