add-e2e-test

Scaffold Playwright end-to-end tests with page objects and fixtures.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/michaelayoade/dotmac_crm --skill add-e2e-test-michaelayoade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-e2e-test
Source: https://github.com/michaelayoade/dotmac_crm/tree/main/.claude/skills/add-e2e-test
Command: npx skills add https://github.com/michaelayoade/dotmac_crm --skill add-e2e-test-michaelayoade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly add reliable Playwright end-to-end tests by standardizing page objects, fixtures, and test scenarios instead of writing everything from scratch.

Core Features & Use Cases

  • Page-object-first scaffolding: Generates page object structure for list and detail pages that use consistent BasePage patterns.
  • Fixture-aligned testing: Produces tests that attach to the correct portal authentication fixtures (like admin_page) and shared settings.
  • Scenario templates: Supports common flows such as page load, list assertions, and navigating from list to detail pages.

Quick Start

Ask the AI to scaffold a new E2E test for the admin tickets list and detail pages by providing the page/flow description you want to cover.

Frequently Asked Questions about add-e2e-test

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

FAQPage Schema
How do I scaffold Playwright E2E tests with page objects and fixtures?

To scaffold Playwright E2E tests, provide a page or flow description to the AI. It generates page objects using BasePage patterns, attaches to portal authentication fixtures, and creates scenario templates for list and detail pages.

What's the best way to add end-to-end test coverage for list-to-detail page flows?

Use scenario templates designed for list-to-detail navigation flows. These templates generate tests that match existing repository conventions and integrate with shared conftest helpers and page objects.

Does this E2E test scaffolding approach work with environment-based authentication?

Yes, generated tests require environment-based authentication via E2E_* settings. They attach to portal authentication fixtures like admin_page defined in your conntest.

Can I generate Playwright tests for different user roles like admin, customer, and vendor?

Yes, you can generate tests for admin, customer, vendor, and reseller portals. The scaffolding attaches to the correct portal authentication fixtures to support each role's page-load and list-to-detail flows.

How do I match new E2E tests to existing repository test conventions?

The scaffolding matches existing conventions by integrating with your tests/playwright directory, utilizing established BasePage patterns, conftest fixtures, and shared helpers already present in your codebase.