init

Solid

Set up Playwright in a project. Use when user says "set up playwright", "add e2e tests", "configure playwright", "testing setup", "init playwright", or "add test infrastructure".

AI & Automation 46 stars 7 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 84/100

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

Skill Content

# Initialize Playwright Project Set up a production-ready Playwright testing environment. Detect the framework, generate config, folder structure, example test, and CI workflow. ## Steps ### 1. Analyze the Project Use the `Explore` subagent to scan the project: - Check `package.json` for framework (React, Next.js, Vue, Angular, Svelte) - Check for `tsconfig.json` → use TypeScript; otherwise JavaScript - Check if Playwright is already installed (`@playwright/test` in dependencies) - Check for existing test directories (`tests/`, `e2e/`, `__tests__/`) - Check for existing CI config (`.github/workflows/`, `.gitlab-ci.yml`) ### 2. Install Playwright If not already installed: ```bash npm init playwright@latest -- --quiet ``` Or if the user prefers manual setup: ```bash npm install -D @playwright/test npx playwright install --with-deps chromium ``` ### 3. Generate `playwright.config.ts` Adapt to the detected framework: **Next.js:** ```typescript import { defineConfig, devices } from '@playwright/test'; export default defineConfig({ testDir: './e2e', fullyParallel: true, forbidOnly: !!process.env.CI, retries: process.env.CI ? 2 : 0, workers: process.env.CI ? 1 : undefined, reporter: [ ['html', { open: 'never' }], ['list'], ], use: { baseURL: 'http://localhost:3000', trace: 'on-first-retry', screenshot: 'only-on-failure', }, projects: [ { name: "chromium", use: { ...devices['Desktop Chrome'] } }, { name: "firefox", use: { ...

Details

Author
adriannoes
Repository
adriannoes/awesome-agentic-ai
Created
9 months ago
Last Updated
3 days ago
Language
Jupyter Notebook
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Listed

playwright-testing

E2E testing with Playwright - Page Objects, cross-browser, CI/CD

0 Updated today
lciacci
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 today
M4NUSH7
Testing & QA Listed

playwright

When the user wants to design, implement, debug, stabilize, or scale Playwright tests. Use when the user mentions "Playwright," "playwright.config.ts," "page.locator," "page.getByRole," "browser context," "fixtures," "test.beforeEach," "trace viewer," "codegen," "Playwright Test," "Playwright MCP," "PWT," "WebKit testing," or "cross-browser." For Cypress-specific questions see cypress. For Selenium-specific questions see selenium. For CI sharding and parallelism see ci-test-orchestration. For screenshot diffing see visual-regression.

1 Updated 2 days ago
aks-builds