e2e

Generate and run Playwright end-to-end tests across Chrome, Firefox, and Safari.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Eotel/claude-marketplace --skill e2e-eotel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/Eotel/claude-marketplace/tree/main/plugins/base/skills/e2e
Command: npx skills add https://github.com/Eotel/claude-marketplace --skill e2e-eotel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and execution of end-to-end tests to validate critical user flows, reducing manual QA effort and accelerating release cycles.

Core Features & Use Cases

  • Generate test journeys for typical user flows and edge cases.
  • Run E2E tests across multiple browsers (Chrome, Firefox, Safari).
  • Capture artifacts (screenshots, videos, traces) on failures and generate reports.
  • Upload HTML reports and JUnit XML for CI integration.
  • Identify flaky tests and quarantine or retry them.

Quick Start

Create and run a Playwright-based end-to-end test for a representative user journey.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I generate Playwright E2E tests for user flows?

You can generate Playwright E2E tests for user flows by analyzing critical journeys and automatically creating Page Object Model based tests. The automation targets typical user paths and edge cases to validate application behavior without manual scripting.

Can I run E2E tests across Chrome, Firefox, and Safari?

Yes, you can run E2E tests across Chrome, Firefox, and Safari. The execution validates critical user flows simultaneously on all three browsers to ensure multi-browser coverage and identify browser-specific issues during QA workflows.

Does Playwright E2E testing capture screenshots and videos on failure?

Yes, Playwright E2E testing captures failure artifacts including screenshots, videos, and traces. It automatically collects these artifacts when a test fails and generates comprehensive reports to help debug issues faster.

How do I upload HTML reports and JUnit XML for CI integration?

You upload HTML reports and JUnit XML for CI integration after the E2E test execution completes. The automation generates both formats to integrate test results directly into continuous integration pipelines and QA reporting systems.

What is the best way to identify and handle flaky tests in E2E automation?

The best way to identify flaky tests in E2E automation is by running test suites and monitoring for inconsistent results. The system detects flaky tests and can automatically quarantine or retry them to maintain reliable CI pipelines.

Do I need existing tests to use this E2E automation, or does it create them from scratch?

You do not need existing tests to use this E2E automation because it creates them from scratch. It analyzes your user flows and generates Page Object Model based tests automatically, reducing manual QA effort and accelerating release cycles.