skills.rest
DGouron
DGouronCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

e2e

Automate Playwright end-to-end testing workflows with structured test organization.

41|7|Updated Jan 30, 2026
Search Tags:#debugging#playwright#ci-cd#e2e-testing#api-testing#test-organization#test-automation
One-click install
npx skills add https://github.com/DGouron/review-flow --skill e2e-dgouron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/DGouron/review-flow/tree/main/.claude/skills/e2e
Command: npx skills add https://github.com/DGouron/review-flow --skill e2e-dgouron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Playwright end-to-end testing often requires structured test scaffolding, stable environments, and clear guidelines to debug flaky tests. This guide helps software teams create reliable e2e tests, quickly diagnose flakiness, and test API endpoints within integrated workflows.

Core Features & Use Cases

  • Organized test architecture with fixtures, specs, and utilities under src/tests/e2e/.
  • Deterministic execution and debugging patterns using Playwright Test, setup hooks, and reusable helpers.
  • Practical workflows for creating new tests, debugging flaky scenarios, and validating API endpoints in CI.

Quick Start

Create a new e2e test by placing your spec under src/tests/e2e/specs and run yarn e2e to execute all tests.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I structure Playwright e2e tests in my project?▼

Playwright e2e tests should be organized under a dedicated src/tests/e2e directory, separating fixtures, specs, and utilities to maintain a scalable test architecture. This layout keeps test automation deterministic and familiar for CI workflows.

What is the best way to debug flaky Playwright tests?▼

Debugging flaky Playwright tests requires deterministic execution patterns using setup hooks, reusable helpers, and dedicated debugging commands like e2e:debug. This approach isolates flakiness and validates stable behavior across feature branches.

Can I validate API endpoints using Playwright test automation?▼

Playwright test automation supports validating API endpoints directly within integrated e2e workflows. You can test API responses across feature branches or CI pipelines using the same structured project layout and familiar commands.

How do I run e2e tests in CI using Playwright?▼

Running e2e tests in CI involves executing familiar Playwright Test commands like yarn e2e and generating reports using test:e2e:report. This validates application workflows across feature branches using deterministic execution patterns.

Do I need specific test organization for Playwright e2e testing?▼

Playwright e2e testing requires structured test organization with dedicated directories for fixtures, specs, and utilities under src/tests/e2e. This scaffolding ensures stable environments and clear guidelines for debugging flaky tests.

Related Skills

Explore More Software Engineering Skills→
EmeaAppGbbEmeaAppGbb

e2e-generation

Generate Playwright end-to-end test specs and Page Object Models from UI/UX flow walkthroughs.

Official
Advanced
oxieoxie

staging-deployment-phase

Automate staging deployment with auto-merge for merged pull requests.

Community
Intermediate
ShunmeiChoShunmeiCho
1

tdd-workflow

Guide Test-Driven Development workflows with Jest, Vitest, and Playwright.

Community
Advanced
rnavarychrnavarych
14

role-aqa:e2e-testing

Guide end-to-end test automation across Playwright, Cypress, Selenium, and WebdriverIO.

Community
Advanced