e2e-testing

Configure Playwright E2E suites with Page Object Model and CI artifact uploads.

58|5|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/mukiwu/muki-ai-plugins --skill e2e-testing-mukiwu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/mukiwu/muki-ai-plugins/tree/main/plugins/shipshape-skills/skills/e2e-testing
Command: npx skills add https://github.com/mukiwu/muki-ai-plugins --skill e2e-testing-mukiwu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides practical patterns and configurations to reduce flakiness, speed up debugging, and streamline end-to-end testing so teams can trust automated Playwright suites and get reliable feedback faster.

Core Features & Use Cases

  • Test Organization: Recommended directory layout, fixtures, and test file structure for scalable suites.
  • Page Object Model: Examples and idioms for encapsulating UI interactions to improve readability and reduce duplication.
  • Flaky Test Strategies: Detection, quarantine, retries, conditional skips, and common root-cause fixes for race conditions, network timing, and animation issues.
  • Artifact Management & CI: Guidance for screenshots, traces, videos, HTML/JUnit/JSON reports, and GitHub Actions workflows to run tests and upload artifacts.
  • Specialized Scenarios: Wallet/Web3 testing, financial/critical-flow safeguards, multi-browser and mobile projects, and environment-aware CI settings.

Quick Start

Run the Playwright E2E suite in tests/e2e with retries enabled and collect screenshots, traces, and the HTML report for any failing tests.

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 E2E tests caused by race conditions and network timing?

Playwright E2E tests can be organized using a recommended directory layout, fixtures, and test file structure, alongside the Page Object Model to encapsulate UI interactions for scalable and maintainable suites.

How do I configure Playwright CI workflows to upload HTML, JUnit, and JSON artifacts?

Playwright CI workflows can be configured to generate deterministic HTML, JUnit, and JSON reports, using GitHub Actions steps to run tests across browsers and upload the captured artifacts.

How do I capture screenshots, traces, and videos for failing Playwright tests?

Playwright configurations support capturing screenshots, traces, and videos as artifacts, providing deterministic outputs that speed up debugging for failing end-to-end tests.

Does this Playwright testing guidance support Web3 wallet and mobile browser scenarios?

Yes, the Playwright testing patterns include specialized scenarios for Web3 wallet testing, financial critical-flow safeguards, and multi-browser mobile projects with environment-aware settings.