test-e2e

Orchestrate Playwright end-to-end testing workflows for UI components.

1|Updated Sep 15, 2023
One-click install
npx skills add https://github.com/emiljuchnikowski/smartsoft001 --skill test-e2e-emiljuchnikowski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-e2e
Source: https://github.com/emiljuchnikowski/smartsoft001/tree/main/.claude/skills/test-e2e
Command: npx skills add https://github.com/emiljuchnikowski/smartsoft001 --skill test-e2e-emiljuchnikowski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the creation and maintenance of end-to-end Playwright tests for UI components, reducing manual setup time and ensuring consistency across projects.

Core Features & Use Cases

  • Scaffold an E2E Playwright project when absent
  • Inject data-testid attributes into component templates
  • Generate Page Objects and test specs aligned to components
  • Execute tests with deterministic Playwright runs and report results
  • Support both changed components and explicit path inputs

Quick Start

Initiate the E2E workflow for your target components or changed files to scaffold, instrument, and run tests.

Frequently Asked Questions about test-e2e

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

FAQPage Schema
How do I automate Playwright E2E test generation for UI components?

Playwright E2E test generation is automated by scaffolding an Nx project, injecting data-testid attributes into component templates, generating Page Objects and test specs, and executing deterministic test runs.

What is the best way to scaffold a Playwright and Nx E2E project?

Scaffold a Playwright and Nx E2E project by initiating an automated workflow that sets up the testing infrastructure, injects required data-testid attributes, generates Page Objects, and creates aligned test specs for your UI components.

Do I need TypeScript and Nx to run automated Playwright E2E workflows?

Yes, TypeScript, Playwright, and Nx are required dependencies to enforce deterministic setup, safe data-testid attribute injection, and automated test execution for UI components.

How does injecting data-testid attributes help with Playwright E2E testing?

Injecting data-testid attributes provides deterministic selectors for Playwright E2E tests, enabling generated Page Objects and test specs to reliably target UI components without relying on fragile CSS or XPath selectors.

Can I generate Page Objects and test specs only for changed UI components?

Yes, the E2E workflow supports both changed component scenarios and explicit path inputs, allowing you to generate Page Objects, inject data-testid attributes, and run test specs exclusively for targeted files.

What are the limitations of automating E2E test workflows with Playwright and Nx?

Limitations include a strict dependency on Playwright, Nx, and TypeScript, meaning projects outside this stack cannot use the workflow, and test execution relies entirely on successful data-testid attribute injection.