e2e-testing

Build stable Playwright end-to-end test suites with page objects and retries.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill e2e-testing-mostafa-ismail-2004
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/mostafa-ismail-2004/codex-plugin/tree/main/skills/e2e-testing
Command: npx skills add https://github.com/mostafa-ismail-2004/codex-plugin --skill e2e-testing-mostafa-ismail-2004

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you build reliable end-to-end test suites that catch real user flow issues without wasting time on brittle selectors, timing flakiness, or inconsistent CI runs.

Core Features & Use Cases

  • Playwright Test Design: Organize tests, fixtures, and page objects for maintainable browser automation.
  • Flake Reduction: Apply waits, retries, quarantines, and stability patterns to reduce false failures.
  • CI/CD Readiness: Configure browsers, reporters, artifacts, and web server setup for repeatable pipeline execution.
  • Use Case: Use this Skill when you need to validate login, search, checkout, or other critical user journeys across browsers and capture screenshots, traces, and videos on failure.

Quick Start

Use the e2e-testing skill to design a stable Playwright test structure for my app and show me how to reduce flakiness in CI.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I reduce flaky Playwright tests in CI pipelines?

Reduce flaky Playwright tests by applying targeted waits, retries, quarantines, and stability patterns. This Skill helps configure test suites to minimize false failures and ensure reliable execution across local development and CI pipelines.

What is the best way to structure Playwright page object models for maintainable browser automation?

Structure Playwright page object models by organizing tests, fixtures, and page objects for maintainable browser automation. This approach ensures reliable execution when validating critical user journeys like login, search, and checkout.

How do I capture screenshots, traces, and videos on Playwright test failures?

Capture screenshots, traces, and videos on Playwright test failures by configuring reporters and artifact capture. This Skill sets up artifact collection to help debug inconsistent CI runs and analyze browser automation failures.

Can I use Playwright to validate critical user journeys like checkout and wallet flows?

Yes, you can use Playwright to validate critical user journeys like checkout, wallet, login, and search flows. This Skill builds stable end-to-end test suites to catch real user flow issues across browsers without wasting time on brittle selectors.

Why does my Playwright browser automation fail inconsistently across local and CI environments?

Playwright browser automation fails inconsistently due to timing flakiness, brittle selectors, and improper web server setup. This Skill addresses these issues by configuring browsers, reporters, and targeted waits for repeatable pipeline execution.

Do I need specific CI/CD configuration to run stable Playwright end-to-end test suites?

You need CI/CD readiness configuration including browsers, reporters, artifacts, and web server setup for repeatable pipeline execution. This Skill helps configure these elements to ensure stable Playwright end-to-end test suites across environments.