e2e-testing

Automates end-to-end web testing with Playwright MCP and regime-driven YAML workflows.

17|1|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/mhylle/claude-skills-collection --skill e2e-testing-mhylle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/mhylle/claude-skills-collection/tree/main/skills/e2e-testing
Command: npx skills add https://github.com/mhylle/claude-skills-collection --skill e2e-testing-mhylle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill automates end-to-end web testing for modern applications, enabling teams to observe, document, and analyze test scenarios without performing manual validation.

Core Features & Use Cases

  • Three-mode workflow: setup (define test regimes), run (execute tests), and report (analyze results).
  • Regime-driven discovery: automatically discovers undocumented paths and flaky areas during test execution.
  • Evidence-rich reports: generates both human-readable and machine-readable outputs, with evidence bundles and historical context.

Quick Start

To begin, configure a test regime under tests/e2e/test_regime.yml, then run the e2e-testing skill in "setup" or "run" mode to generate reports and discoveries.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I automate end-to-end web testing with Playwright?

You can automate end-to-end web testing by configuring a test regime in a YAML file and executing it through setup, run, and report modes. This workflow handles test discovery, execution, and evidence-rich output generation.

What is a test regime and how does it help with e2e regression testing?

A test regime is a YAML-defined configuration that drives end-to-end test discovery and execution. It enables regime-driven discovery of undocumented paths and flaky areas, ensuring comprehensive regression testing coverage.

How do I identify and analyze flaky tests in my web application?

You can identify flaky tests by running your e2e test regime and analyzing the generated reports. The system captures evidence and historical context during execution, highlighting flaky areas and regressions in both human-readable and machine-readable formats.

Does this e2e testing workflow support machine-readable test reports?

Yes, the e2e testing workflow generates both human-readable and machine-readable outputs. The report mode analyzes execution results, producing evidence bundles and historical context suitable for automated pipeline consumption.

How do I set up a YAML test regime for web automation?

To set up a YAML test regime, define your configuration under the tests/e2e/test_regime.yml file path. Running the e2e-testing skill in setup mode will process this configuration to establish your automated test workflow.

Can I capture test evidence and historical context during automated web testing?

Yes, evidence capture and historical context are core features of this automated web testing workflow. During the run and report modes, the system automatically bundles execution evidence to document regressions and flaky test behavior.