generate

Solid

Generate 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".

AI & Automation 57 stars 12 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
59
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Generate Playwright Tests Generate production-ready Playwright tests from a user story, URL, component name, or feature description. ## Input `$ARGUMENTS` contains what to test. Examples: - `"user can log in with email and password"` - `"the checkout flow"` - `"src/components/UserProfile.tsx"` - `"the search page with filters"` ## Steps ### 1. Understand the Target Parse `$ARGUMENTS` to determine: - **User story**: Extract the behavior to verify - **Component path**: Read the component source code - **Page/URL**: Identify the route and its elements - **Feature name**: Map to relevant app areas ### 2. Explore the Codebase Use the `Explore` subagent to gather context: - Read `playwright.config.ts` for `testDir`, `baseURL`, `projects` - Check existing tests in `testDir` for patterns, fixtures, and conventions - If a component path is given, read the component to understand its props, states, and interactions - Check for existing page objects in `pages/` - Check for existing fixtures in `fixtures/` - Check for auth setup (`auth.setup.ts` or `storageState` config) ### 3. Select Templates Check `templates/` in this plugin for matching patterns: | If testing... | Load template from | |---|---| | Login/auth flow | `../pw/templates/auth/login.md` | | CRUD operations | `templates/crud/` | | Checkout/payment | `templates/checkout/` | | Search/filter UI | `templates/search/` | | Form submission | `templates/forms/` | | Dashboard/data | `templates/dashboard/` | | Settings pa...

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

Testing & QA Solid

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.

13 Updated today
voidmatcha
Testing & QA Listed

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.

0 Updated 3 days ago
eduramos21
Testing & QA Listed

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.

1 Updated 1 months ago
M4NUSH7