e2e-testing

Implements Playwright E2E test suites with Page Object Model, CI integration, and flaky test handling.

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/adamreger/ecc-antigravity --skill e2e-testing-adamreger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/adamreger/ecc-antigravity/tree/main/skills/e2e-testing
Command: npx skills add https://github.com/adamreger/ecc-antigravity --skill e2e-testing-adamreger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @playwright/test.

What problem does it solve? End-to-end tests are often slow, flaky, and hard to maintain. This Skill provides proven Playwright patterns for structuring test suites, stabilizing unreliable tests, managing artifacts, and integrating E2E testing into CI/CD pipelines. ## Core Features & Use Cases - Page Object Model Patterns: Encapsulate page interactions in reusable classes with locators and action methods, keeping test files clean and maintainable. - Flaky Test Management: Diagnose race conditions, network timing, and animation issues, then apply quarantine strategies with test.fixme and conditional skips. - CI/CD & Artifact Management: Configure GitHub Actions workflows, HTML/JUnit/JSON reporters, screenshots, videos, and traces for debugging failures. - Use Case: A team shipping a web app needs reliable browser tests across Chromium, Firefox, WebKit, and mobile viewports. Use this Skill to scaffold a Playwright config with retries, parallel workers, and failure artifacts, then write POM-based tests for critical flows like auth and checkout. ## Quick Start Write a Playwright E2E test suite for my login flow using the Page Object Model pattern with CI configuration.

Frequently Asked Questions about e2e-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure Playwright tests with Page Object Model?▼

Create a class per page that exposes locators and action methods, such as goto, search, and getItemCount. Tests then instantiate the page object in beforeEach and call its methods, keeping assertions separate from interaction logic.

How to fix flaky Playwright tests in CI?▼

Replace arbitrary waitForTimeout calls with condition-based waits like waitForResponse or locator auto-waiting. Quarantine known flaky tests with test.fixme or conditional test.skip, and reproduce flakiness locally using --repeat-each=10.

Does Playwright support testing across multiple browsers?▼

Yes, Playwright projects in the config file run the same tests across Chromium, Firefox, WebKit, and mobile device profiles like Pixel 5. Each project can have its own device and viewport settings.

How do I capture screenshots and videos on Playwright test failure?▼

Set screenshot to 'only-on-failure', video to 'retain-on-failure', and trace to 'on-first-retry' in the use block of playwright.config.ts. Artifacts are uploaded in CI via actions/upload-artifact for later inspection.

Can Playwright test Web3 wallet connection flows?▼

Yes, mock the wallet provider with context.addInitScript to inject a fake window.ethereum object that responds to eth_requestAccounts and eth_chainId. Tests can then verify connect-wallet UI behavior without a real wallet.