e2e-testing

Automate Playwright end-to-end testing with Page Object Model and TypeScript checks.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/vexjoy-agent --skill e2e-testing-notque
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/notque/vexjoy-agent/tree/main/skills/testing/e2e-testing
Command: npx skills add https://github.com/notque/vexjoy-agent --skill e2e-testing-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents unreliable end-to-end tests from being “green” without evidence by enforcing a Playwright workflow that generates artifacts and only advances when required gates pass.

Core Features & Use Cases

  • Scaffold with diagnostics: Creates a consistent Playwright project structure and configures failure-first artifacts (screenshots, traces, videos) for actionable debugging.
  • Deterministic build discipline: Forces Page Object Model (POM) usage with data-testid selectors and verifies TypeScript compilation before generating/using tests.
  • Evidence-based run workflow: Executes the test suite, quarantines confirmed flaky tests with test.fixme(), and never silently delete failing coverage.
  • Validated reporting output: Parses and validates playwright-results.json, then produces a structured e2e-report.md as the completion gate.

Quick Start

Run the e2e-testing skill to scaffold a Playwright E2E project, write POM-backed specs, execute the suite, quarantine flakiness, and generate an e2e-report.md using Playwright artifacts.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I stop Playwright E2E tests from being flaky and passing without evidence?

To stop Playwright E2E tests from being flaky, enforce an evidence-based workflow that quarantines confirmed flaky tests using test.fixme(), captures failure-first artifacts like traces and videos, and validates JSON results before advancing. This prevents suites from going green without proof.

How to set up a Playwright project using Page Object Model and TypeScript?

Set up a Playwright project using Page Object Model and TypeScript by scaffolding a consistent project structure, forcing POM usage with data-testid selectors, and verifying TypeScript compilation before generating or running tests to ensure deterministic build discipline.

What is the best way to validate Playwright test reporting for CI gates?

The best way to validate Playwright test reporting for CI gates is to parse and validate playwright-results.json, then generate a structured e2e-report.md as the completion gate. This enforces scaffold, build, run, and validate phases using required artifacts.

Does this E2E testing workflow require TypeScript compilation checks before running?

Yes, this E2E testing workflow requires TypeScript compilation checks before running. It enforces deterministic build discipline by verifying TypeScript compilation and applying Page Object Model usage with data-testid selectors prior to test execution.

Why does my E2E suite silently delete failing test coverage?

Your E2E suite silently deletes failing test coverage when it lacks an enforced run workflow. An evidence-based workflow executes the suite, quarantines flaky tests with test.fixme(), and never silently deletes failing coverage, ensuring reliable verification.