e2e-run

Run Playwright E2E tests with automatic project detection and YAML summaries.

1|2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill e2e-run-parisgroup-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-run
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/e2e-run
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill e2e-run-parisgroup-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes friction when running end-to-end Playwright tests in a monorepo by automatically detecting the correct test project, applying optimized wait strategies, performing pre-flight environment checks, and producing machine-readable results for downstream analysis.

Core Features & Use Cases

  • Project Auto-Detection: Resolve exact names, aliases, or file/path matches using apps/web/e2e/e2e-projects.json so the correct Playwright --project flag is selected.
  • Pre-flight Safety Checks: Validate database connection counts and optionally restart the test database container to avoid pool exhaustion before running tests.
  • Structured Reporting & Triage: Execute pnpm test:e2e with the detected project, capture output, generate a YAML result with counts and categorized failures, and support follow-up analysis such as batch approvals or deeper diagnostics.
  • Use Case: Run targeted suites like admin-tests from CI or developer machines, automatically recover from common infra issues, and feed results into an e2e-analyze workflow.

Quick Start

Run the e2e-run skill with the target name to auto-detect the Playwright project, perform pre-flight checks, execute the tests, and write a structured YAML summary to apps/web/e2e-run-result.yaml.

Frequently Asked Questions about e2e-run

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

FAQPage Schema
How do I run targeted Playwright E2E tests in a monorepo without manually specifying the project?

To run Playwright E2E tests automatically in a monorepo, the skill detects the correct project from apps/web/e2e/e2e-projects.json using exact names, aliases, or file path matches, then executes pnpm test:e2e with the resolved --project flag.

What are the best ways to prevent database pool exhaustion during Playwright E2E test runs?

Preventing database pool exhaustion involves performing pre-flight safety checks that validate database connection counts and optionally restart the test database container before executing the Playwright E2E test suite.

How do I generate structured E2E test reports for CI workflows and downstream analysis?

Generating structured E2E test reports involves executing the targeted Playwright tests, capturing output, and emitting a YAML summary file containing execution metadata, counts, and categorized failures for downstream CI analysis.

Can I use fuzzy project resolution to select a specific Playwright test suite in a pnpm monorepo?

Yes, fuzzy and path-based project resolution is supported to select the correct Playwright test suite in a pnpm monorepo by matching target names against the aliases and file matches defined in e2e-projects.json.

Why does my CI E2E test run fail before executing due to infrastructure issues?

CI E2E test runs may fail due to infrastructure issues like database pool exhaustion, which this approach mitigates by applying optimized wait strategies and performing pre-flight environment checks before test execution.

Does e2e-run support automatic recovery from common infrastructure issues during Playwright test execution?

Yes, e2e-run supports automatic recovery from common infrastructure issues by validating database connections and optionally restarting the test database container prior to running the Playwright E2E tests.