skills.rest
incubateur-ademe
incubateur-ademeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

create-e2e-test

Automate Playwright end-to-end tests using page objects and fixtures.

45|3|Updated Jul 10, 2023
Search Tags:#typescript#playwright#fixtures#e2e-testing#testing-patterns#page-objects#qa-automation
One-click install
npx skills add https://github.com/incubateur-ademe/benefriches --skill create-e2e-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-e2e-test
Source: https://github.com/incubateur-ademe/benefriches/tree/main/.claude/skills/create-e2e-test
Command: npx skills add https://github.com/incubateur-ademe/benefriches --skill create-e2e-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables automated end-to-end testing of web applications using Playwright with a page object model and fixtures, reducing manual QA workload and accelerating validation of complex user flows.

Core Features & Use Cases

  • Page Object Pattern: organize test interactions into reusable page classes.
  • Fixture-driven setup: centralize authentication and data setup for consistent test runs.
  • Feature-based test structure: align tests with application features and user flows to improve maintainability.

Quick Start

Run the end-to-end test suite using the Playwright-based patterns described in this Skill. Example commands and directory structure follow the repository conventions in apps/e2e-tests/pages, apps/e2e-tests/fixtures, and apps/e2e-tests/tests. pnpm --filter e2e-tests test:e2e tests//.spec.ts

Frequently Asked Questions about create-e2e-test

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

FAQPage Schema
How do I structure Playwright e2e tests using page objects and fixtures?▼

Playwright e2e tests using page objects and fixtures require organizing reusable page classes under apps/e2e-tests/pages, centralizing setup in apps/e2e-tests/fixtures, and grouping feature-based spec files in apps/e2e-tests/tests to generate maintainable validation results.

What is the best way to automate end-to-end testing of complex user flows in TypeScript?▼

Automating end-to-end testing of complex TypeScript user flows is best handled by applying a page object model and fixture-driven setup via Playwright, which reduces manual QA workload and accelerates UI flow validation across repository patterns.

Do I need a specific directory structure to run Playwright e2e tests with this pattern?▼

Yes, this Playwright e2e testing pattern requires a TypeScript setup with a repository structure specifically under apps/e2e-tests, containing dedicated directories for pages, fixtures, and tests to generate reliable, maintainable results.

How do I execute the e2e test suite for feature-based Playwright specs?▼

To execute the e2e test suite for feature-based Playwright specs, run the command pnpm --filter e2e-tests test:e2e tests/**/**.spec.ts, which targets spec files according to project conventions to generate reliable test results.

When should I use fixture-driven setup in Playwright e2e testing?▼

Fixture-driven setup in Playwright e2e testing should be used to centralize authentication and data setup, ensuring consistent test runs and reducing manual QA workload when validating complex user flows to generate reliable results.

Related Skills

Explore More Software Engineering Skills→
nirukk52nirukk52
1

e2e-testing

Automate ScreenGraph end-to-end UI validation with Playwright and .env configuration.

Community
Intermediate
UniswapUniswap
5.5k

web-e2e

Automate end-to-end Playwright tests for the Uniswap web application.

Official
Advanced
RomualdPRomualdP

Zero Warnings Enforcer

Enforce zero ESLint warnings and TypeScript errors via root-cause fixes.

Community
Advanced
simotasimota
68

Voyager

Builds end-to-end browser automation suites with Playwright, Cypress, or WebdriverIO.

Community
Advanced