e2e-playwright

What This Skill Does

The e2e-playwright skill provides OpenClaw with specialized capabilities for end-to-end testing, browser automation, and web interface verification. It leverages the Playwright framework to enable robust, reliable, and fast automated testing across multiple browser engines including Chromium, Firefox, and WebKit. This skill excels at creating maintainable test suites using the Page Object Model (POM), managing complex authentication states, and handling modern web application features like dynamic content, shadow DOMs, and asynchronous network requests.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/anton-abyzov/sw-e2e-playwright

Use Cases

• Automated Regression Testing: Ensuring critical user flows (like sign-up or checkout) remain functional after code deployments.
• Browser Compatibility Testing: Validating your web application layout and functionality consistently across different browser rendering engines.
• Debugging Flaky Tests: Utilizing Playwright's trace viewer and auto-waiting mechanisms to identify and resolve intermittent test failures.
• API Mocking & Network Interception: Simulating complex backend responses to test frontend edge cases without requiring a live backend environment.
• Data Scraping & Form Automation: Automating repetitive data entry tasks or extracting information from complex web pages that require JavaScript execution.

Example Prompts

1. "Create a Playwright test file using the Page Object Model that checks if the dashboard profile settings update correctly when I save a new name."
2. "Help me debug this flaky test; it keeps failing on the login screen specifically in WebKit, even though it passes on Chromium."
3. "Write a custom Playwright fixture that logs in as an admin user and sets a specific local storage key before running the test suite."

Tips & Limitations

• Adopt POM: Always structure your tests using the Page Object Model to minimize maintenance when UI selectors change.
• Prefer Locators: Use getByRole or getByLabel instead of CSS selectors to make tests more resilient to design changes.
• Avoid Hard Waits: Never use page.waitForTimeout(). Rely on Playwright's built-in auto-waiting for actions like click() or fill().
• Environment Variables: Ensure sensitive data like credentials are handled via environment variables rather than hard-coded in your test scripts.
• Resource Intensity: Note that running extensive E2E suites can be resource-intensive; utilize parallelization settings in playwright.config.ts for larger projects.