e2e-testing

Configure Playwright end-to-end test suites with Page Object Model and CI/CD integration.

26|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/BinyaminEden/claude-combine --skill e2e-testing-binyamineden
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/BinyaminEden/claude-combine/tree/main/skills/e2e-testing
Command: npx skills add https://github.com/BinyaminEden/claude-combine --skill e2e-testing-binyamineden

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the widespread issue of flaky, hard-to-maintain end-to-end (E2E) test suites that break with minor UI changes, are time-consuming to debug, and fail to integrate reliably with CI/CD pipelines, diverting developer time away from feature work to test maintenance.

Core Features & Use Cases

  • Page Object Model (POM) Implementation: Reusable page object classes that eliminate test duplication and simplify updates when UI selectors change.
  • Flaky Test Mitigation: Proven patterns to quarantine flaky tests, identify root causes like race conditions and network timing issues, and fix them with proper auto-waiting strategies.
  • CI/CD Integration: Pre-configured Playwright settings and GitHub Actions workflow templates optimized for CI environments, with built-in artifact management for reports, screenshots, and traces.
  • Specialized Testing Patterns: Ready-to-use templates for Web3 wallet connection testing and financial critical flow testing with appropriate safety guardrails. Use case: For example, if your team is seeing 30% of E2E tests fail randomly in CI, use this Skill to implement proper wait strategies, quarantine known flaky tests, and configure retries and artifact collection to cut debugging time in half.

Quick Start

Use the e2e-testing skill to generate a production-ready Playwright test suite with POM structure, CI/CD configuration, and flaky test mitigation patterns for your existing web application.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I fix flaky Playwright tests in CI/CD pipelines?

Fix flaky Playwright tests by implementing proper auto-waiting strategies to handle race conditions, quarantining known flaky tests, and configuring retries with artifact collection to halve debugging time in CI.

How do I structure Playwright test files using the Page Object Model?

Structure Playwright tests using the Page Object Model by creating reusable page object classes that eliminate test duplication and simplify updates when UI selectors change, ensuring maintainable E2E test suites.

Can I automate Web3 wallet connection testing with Playwright?

Yes, you can automate Web3 wallet connection testing with Playwright using ready-to-use specialized testing templates that include appropriate safety guardrails for financial critical flows and Web3 environments.

What is the best way to configure Playwright for GitHub Actions CI?

The best way to configure Playwright for GitHub Actions CI is using pre-configured settings and workflow templates optimized for CI environments, with built-in artifact management for reports, screenshots, and traces.

Why do my end-to-end tests break with minor UI changes and how do I stop it?

End-to-end tests break with minor UI changes due to hardcoded selectors; stop this by implementing the Page Object Model to centralize selectors in reusable classes, making updates simple and preventing widespread test failures.