skills.rest
robinxin
robinxinCOMMUNITY
Explore all skills by this author →
GitHub

e2e-testing

Automate stable Playwright end-to-end tests with Page Object Model and CI/CD integration.

Updated Aug 27, 2026
Search Tags:#testing#e2e#playwright#ci-cd#flaky-tests#pom#artifact-management
One-click install
npx skills add https://github.com/robinxin/AIFlomo --skill e2e-testing-robinxin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/robinxin/AIFlomo/tree/main/.claude/skills/e2e-testing
Command: npx skills add https://github.com/robinxin/AIFlomo --skill e2e-testing-robinxin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

E2E tests for web applications are often brittle and hard to maintain; this skill provides Playwright-based patterns, a Page Object Model approach, alongside configuration, CI/CD guidance, and strategies to manage flaky tests and artifacts.

Core Features & Use Cases

  • Page Object Model wrappers for reusable components
  • Configuration patterns for Playwright projects and CI/CD integration
  • Flaky-test strategies and quarantine approaches
  • Artifact generation and management (screenshots, traces, videos)
  • Real-world use cases across web applications

Quick Start

Implement a Playwright-based E2E test suite using Page Object Model for a stable, CI-ready workflow.

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 E2E tests using the Page Object Model?▼

Playwright E2E tests use the Page Object Model to create reusable component wrappers, organizing test suites for stable web application testing and easier maintenance.

What's the best way to manage flaky tests in a Playwright CI/CD pipeline?▼

Managing flaky tests in Playwright involves applying targeted strategies and quarantine approaches to isolate unstable tests, ensuring reliable CI/CD integration and consistent execution.

How does Playwright artifact management work for failed E2E tests?▼

Playwright artifact management generates screenshots, traces, and videos during E2E test execution, providing visual outputs to debug and analyze failures across web applications.

Can I integrate Playwright test configuration directly into existing CI/CD workflows?▼

Yes, Playwright test configuration provides specific patterns to integrate directly into CI/CD workflows, enabling automated end-to-end testing and artifact generation for web applications.

Why do my Playwright E2E tests fail in CI but pass locally?▼

Playwright E2E tests may fail in CI due to configuration mismatches; applying CI/CD patterns, flaky-test strategies, and artifact management helps diagnose and stabilize execution.

Related Skills

Explore More Software Engineering Skills→
tapanshahtapanshah

init

Initialize Playwright end-to-end testing with configuration and CI workflows.

Community
Advanced
sbalagan22sbalagan22

e2e-testing

Organize Playwright end-to-end tests with Page Object Model and artifact workflows.

Community
Advanced
faionfaionfaionfaion
4

faion-automation-tooling

Automates development workflows with Puppeteer, Playwright, GitHub Actions, Turborepo, pnpm, k6, and Locust.

Community
Advanced
williamzujkowskiwilliamzujkowski
17

e2e-testing

Automate end-to-end web app testing with Playwright or Cypress in CI/CD pipelines.

Community
Intermediate