e2e-testing

Build Playwright end-to-end test suites with page objects and CI artifacts.

Updated May 17, 2022
One-click install
npx skills add https://github.com/kanade0404/dotfiles --skill e2e-testing-kanade0404
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/kanade0404/dotfiles/tree/main/.claude-plugin/skills/e2e-testing
Command: npx skills add https://github.com/kanade0404/dotfiles --skill e2e-testing-kanade0404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams replace brittle, slow, and hard-to-maintain end-to-end tests with stable Playwright workflows that are easier to debug, scale, and trust.

Core Features & Use Cases

  • Page Object Model: Organize selectors and actions into reusable page classes for cleaner tests.
  • Test Reliability: Reduce flakiness with explicit waits, locator-first interactions, retries, and quarantine patterns.
  • CI and Artifact Support: Capture screenshots, traces, videos, and reports so failures are actionable in local runs and continuous integration.
  • Use Case: A web team can use this Skill to design a full Playwright suite for login, search, checkout, and other critical user journeys while keeping failure analysis fast and consistent.

Quick Start

Ask me to design a stable Playwright end-to-end testing setup for your app, including page objects, configuration, flaky-test handling, and CI artifacts.

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 my CI pipeline?

Fix flaky Playwright tests by applying explicit waits, locator-first interactions, retries, and quarantine patterns. This approach ensures stable selector usage and deterministic waits, reducing unreliable test outcomes during CI execution.

What is the best way to organize Playwright end-to-end test suites?

Organize Playwright end-to-end test suites using the Page Object Model to structure selectors and actions into reusable page classes. This method keeps test code clean, maintainable, and scalable for critical user journeys.

How to capture screenshots and traces for failed Playwright tests?

Capture screenshots and traces for failed Playwright tests by configuring artifact reporting during local runs and continuous integration. This yields actionable failure analysis data, including videos and traces, for fast debugging.

Can I use Playwright for cross-browser testing in continuous integration?

Yes, you can use Playwright for cross-browser testing in continuous integration by configuring browser projects. CI/CD integration supports repeatable test automation across multiple browser environments with artifact capture.

Why do my end-to-end tests fail after minor UI changes?

End-to-end tests fail after minor UI changes due to brittle selectors and hard-coded waits. Replacing them with stable selector usage and locator-first interactions ensures deterministic waits and resilient test automation.

How do I set up Playwright configuration tuning for web applications?

Set up Playwright configuration tuning for web applications by adjusting browser projects, retries, and artifact capture settings. This provides stable test execution, deterministic waits, and CI/CD integration for repeatable workflows.