Generate Playwright E2E tests using page object patterns and role-based selectors.
npx skills add https://github.com/cheetah-alo/NegritaOS --skill playwright-cheetah-alo
Please help me install this Agent Skill. Skill: playwright Source: https://github.com/cheetah-alo/NegritaOS/tree/main/.codex/skills/playwright Command: npx skills add https://github.com/cheetah-alo/NegritaOS --skill playwright-cheetah-alo
Playwright E2E test suites often become flaky and expensive when selectors are guessed, page flows aren’t validated end-to-end, and duplicated page-object logic grows uncontrollably.
BasePage, shared helpers, and per-page page objects plus a single spec per page.getByRole and getByLabel, uses getByText only for static content, and falls back to getByTestId when necessary.Generate a Playwright E2E test for the user sign-up flow, using the Playwright MCP exploration workflow if available and creating only the single most relevant test in the existing spec.
High-intent search queries and answers about installing and using this skill.
Stable Playwright E2E tests require prioritizing robust selectors like getByRole and getByLabel over CSS classes, applying page object patterns, and validating complete user flows to reduce flakiness. Use getByText only for static content and getByTestId as a fallback.
A deterministic Playwright page object model enforces a consistent file structure with a BasePage, shared helpers, and per-page page objects, consolidating tests into a single spec file per page to prevent duplicated logic and uncontrolled growth.
Generating Playwright tests for authenticated navigation and form submissions involves applying end-to-end flow verification across single-page or multi-step user journeys, specifically targeting frontend UI testing scenarios including validation and error states.
Playwright MCP exploration helps derive better UI selectors by navigating, snapshotting structure, interacting with real flows, and capturing screenshots to derive selectors from actual UI state rather than guessing, resulting in more reliable frontend automation tests.
Playwright test suites generate too many tests accidentally when user intent is ambiguous, so scope control asks for clarification between a single test and a full suite, preventing accidental over-generation and keeping the spec file focused.
csim-sgGenerate and run Playwright end-to-end tests for the tldraw UI.
kasiopeiyaExecute backend and frontend unit tests with Vitest and generate detailed reports.
Danik911Automate Langfuse Cloud dashboards with Playwright MCP to capture screenshots and extract metrics.
AxelooooDevelops reliable end-to-end test suites for web apps using Playwright and Cypress.