Develop and maintain Playwright E2E tests using Page Object Model and MCP workflows.
npx skills add https://github.com/felipe3dfx/dotfiles --skill playwright-felipe3dfx
Please help me install this Agent Skill. Skill: playwright Source: https://github.com/felipe3dfx/dotfiles/tree/main/skills/playwright Command: npx skills add https://github.com/felipe3dfx/dotfiles --skill playwright-felipe3dfx
This Skill provides a comprehensive framework and best practices for writing reliable, maintainable, and efficient End-to-End (E2E) tests using Playwright, ensuring application quality and stability.
Use the playwright skill to generate a new E2E test for the user login functionality.
High-intent search queries and answers about installing and using this skill.
Maintainable Playwright E2E tests are written using the Page Object Model to structure tests for reusability and readability, ensuring application quality. This approach separates test logic from UI elements, reducing duplication and making updates easier when the UI changes.
The best selector strategy for stable E2E testing involves prioritizing robust selectors to prevent test flakiness. By adhering to strict selector priorities, tests target elements resilient to DOM changes, ensuring consistent execution and validation across different runs.
Manual Control Protocol (MCP) workflow integration works by guiding users to leverage MCP tools for accurate test case creation and validation. This integration ensures that E2E tests are generated and validated accurately within automated testing workflows.
Yes, you can use the Page Object Model to refactor existing E2E test suites. The skill provides test documentation and refactoring guidelines for maintainability, allowing you to restructure tests for improved reusability and readability without losing coverage.
The best way to structure tests for a user authentication flow is developing a full E2E suite using Playwright. This ensures sign-up, login, password reset, and logout processes function correctly and consistently through structured, reusable test components.
Yes, adhering to strict selector priorities is needed to prevent flaky E2E tests. By focusing on robust selectors, the testing framework ensures that test cases target stable elements, maintaining application quality and stability during validation.
ggombeeAutomates Playwright E2E testing environment setup for web applications.
anton-abyzovEliminate flaky Playwright end-to-end test failures across Chromium, Firefox, and WebKit.
Michae2xlAutomate end-to-end web application testing with Playwright and Page Object Model.
etylsarinConfigure Cypress E2E and component tests with CI-ready GitHub Actions.
