Define standards and best practices for Playwright E2E testing in TypeScript.
npx skills add https://github.com/walid-mos/mac-config --skill playwright-walid-mos
Please help me install this Agent Skill. Skill: playwright Source: https://github.com/walid-mos/mac-config/tree/main/claude/.claude/skills/playwright Command: npx skills add https://github.com/walid-mos/mac-config --skill playwright-walid-mos
This Skill establishes best practices for writing robust end-to-end tests that verify real user interactions and visual correctness in a browser environment, ensuring application quality.
Use the playwright skill to write an end-to-end test for the user login journey.
High-intent search queries and answers about installing and using this skill.
To write E2E tests for user journeys, implement the Page Object Model with TypeScript to verify multi-page workflows like login or checkout. This approach establishes standards for selector priority and assertion patterns to ensure reliable browser automation.
Visual regression testing in TypeScript verifies the visual appearance and browser-specific interactions of individual UI components. Establishing component-level E2E testing standards ensures visual correctness across different browsers without relying solely on functional assertions.
Yes, this Playwright testing standard supports network mocking to isolate tests from external dependencies. By mocking network requests, you ensure reliable browser automation and stable CI/CD configurations for your end-to-end test suites.
Yes, you can use the Page Object Model pattern for component-level testing to structure selector priority and assertion patterns. This implementation standardizes both component-level visual regression and full user journey verification across multiple pages.
Standardizing selector priority in Playwright browser automation prevents flaky tests by targeting robust element locators. This standard, combined with strict assertion patterns and CI/CD configurations, guarantees reliable E2E test execution across different browser environments.
Journey-level E2E testing across multiple pages can become slow and brittle if selector priority and network mocking are not properly configured. To mitigate these limitations, maintain strict CI/CD configurations and use the Page Object Model to isolate journey steps.
hakushunWrite Playwright end-to-end tests under e2e/<feature>.spec.ts using page.goto and getByRole.
gajjalaashok75-UIBuilds Playwright-based end-to-end browser test suites for CI/CD pipelines.
matteocervelliGenerate Playwright end-to-end tests using the page object model.
williamzujkowskiAutomate end-to-end web app testing with Playwright or Cypress in CI/CD pipelines.
