e2e-write

Generate Playwright E2E tests with Page Object Model and semantic locators.

4|Updated Jul 12, 2016

Search Tags:#automation #typescript #e2e #playwright #frontend-testing #page-object-model #mobile-testing

Ready to run

npx skills add https://github.com/ProjectEuropa/Europa --skill e2e-write

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-write
Source: https://github.com/ProjectEuropa/Europa/tree/main/.claude/skills/e2e-write
Command: npx skills add https://github.com/ProjectEuropa/Europa --skill e2e-write

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate structured E2E tests efficiently using Playwright with Page Object Model and semantic locators to reduce flakiness and boost test maintainability.

Core Features & Use Cases

Page Object scaffolding under frontend/e2e/pages/
Desktop and mobile test file generation under frontend/e2e
Enforce semantic locators and promote reusable test components

Quick Start

Invoke the e2e-write skill to generate a new Page Object and desktop/mobile spec files for your target page.

Frequently Asked Questions about e2e-write

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

FAQPage Schema

How do I generate Playwright E2E tests using the Page Object Model?▼

Playwright E2E tests using the Page Object Model are generated by scaffolding TypeScript classes and desktop/mobile spec files with semantic locators, placing outputs directly under the frontend/e2e directory.

What is the best way to structure Playwright test files for desktop and mobile?▼

Structuring Playwright test files for desktop and mobile involves generating distinct spec files under frontend/e2e, utilizing scaffolded TypeScript Page Object classes in frontend/e2e/pages/ to enforce reusable test components.

When do I need to scaffold new Page Object classes for frontend testing?▼

Scaffolding new Page Object classes for frontend testing is required when new pages or components are added or after feature implementation, ensuring E2E tests remain robust and maintainable.

Does this approach generate TypeScript files for both desktop and mobile testing?▼

Yes, the approach generates TypeScript files for both desktop and mobile testing, producing separate spec files alongside Page Object scaffolding under frontend/e2e to cover both viewport contexts.

Why should I use Page Objects with Playwright rather than writing raw test scripts?▼

Using Page Objects with Playwright rather than raw test scripts enforces semantic locators and promotes reusable test components, significantly reducing test flakiness and boosting maintainability.

Can I automate E2E test creation without writing boilerplate TypeScript code?▼

Yes, you can automate E2E test creation without writing boilerplate TypeScript code by invoking a tool that scaffolds Page Object classes and exports desktop and mobile spec files following project conventions.