e2e-testing

Build Playwright end-to-end test suites with Page Object Model patterns.

1|Updated Jan 30, 2021
One-click install
npx skills add https://github.com/fideguch/my_dotfiles --skill e2e-testing-fideguch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/fideguch/my_dotfiles/tree/main/claude/skills/e2e-testing
Command: npx skills add https://github.com/fideguch/my_dotfiles --skill e2e-testing-fideguch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Playwright end-to-end testing can be complex and flaky; this skill provides patterns, organization, and configuration guidance to build stable, scalable tests using Page Object Model, with artifact management and CI/CD integration.

Core Features & Use Cases

  • Page Object Model (POM) guidance and sample classes to promote maintainable tests.
  • Test Structure and patterns for auth, features, and API endpoints with clear organization.
  • Playwright configuration and cross-browser project setup, with guidance on CI integration.
  • Flaky test handling patterns, quarantine, and resilience strategies.
  • Artifact management, including screenshots, traces, and videos for debugging.
  • CI/CD integration examples and best practices for automated test runs.

Quick Start

Run the Playwright-based e2e suite against your application to validate authentication, item search, and API end-to-end flows.

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 end-to-end tests using the Page Object Model?

Structure Playwright end-to-end tests using Page Object Model (POM) classes to promote maintainable test organization. This approach encapsulates element locators and interactions within POM classes, separating UI logic from test assertions to build scalable and structured test suites.

Why do my Playwright E2E tests fail randomly and how can I handle flaky tests?

Handle flaky Playwright tests by applying quarantine, resilience strategies, and specific flaky test patterns. This skill provides structured approaches to identify intermittently failing E2E tests and apply resilience patterns to stabilize automated CI/CD runs.

What is the best way to configure Playwright cross-browser testing in CI/CD?

Configure Playwright cross-browser testing in CI/CD using configuration presets and project setup examples. This skill offers integration best practices to run automated E2E test suites across multiple browsers within continuous integration pipelines.

How do I collect Playwright artifacts like screenshots and traces for debugging?

Collect Playwright artifacts like screenshots, traces, and videos through comprehensive artifact management configuration. This skill sets up automatic artifact collection to capture visual evidence and execution traces of E2E test runs, streamlining debugging.