wp-e2e-creator

Generate Playwright E2E tests for WordPress plugins from specification documents.

1|Updated Apr 20, 2025
One-click install
npx skills add https://github.com/j7-dev/wp-power-checkout --skill wp-e2e-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wp-e2e-creator
Source: https://github.com/j7-dev/wp-power-checkout/tree/main/.github/skills/wp-e2e-creator
Command: npx skills add https://github.com/j7-dev/wp-power-checkout --skill wp-e2e-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of robust End-to-End (E2E) tests for WordPress plugins by intelligently identifying edge cases from specification documents.

Core Features & Use Cases

  • Spec Analysis: Parses specification documents to extract key information like features, user roles, and business rules.
  • Edge Case Identification: Systematically identifies boundary conditions related to permissions, data, states, and integrations.
  • Test Matrix Generation: Plans comprehensive test coverage by cross-referencing scenarios, roles, and edge cases.
  • Playwright Test Generation: Produces executable Playwright tests for frontend, admin, and integration layers.
  • Use Case: Given a spec/user-permissions.md file, generate Playwright tests that verify how different user roles (guest, subscriber, admin) interact with a new feature, including scenarios where permissions are unexpectedly revoked or granted.

Quick Start

Use the wp-e2e-creator skill to generate Playwright E2E tests based on the specifications found in the spec/ directory.

Frequently Asked Questions about wp-e2e-creator

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

FAQPage Schema
How do I generate Playwright E2E tests for WordPress plugins from spec documents?

To generate Playwright E2E tests for WordPress plugins, you can use this Skill to parse specification documents, identify edge cases across permissions and data boundaries, and output executable test files. It systematically cross-references user roles and scenarios to build a comprehensive test matrix.

What is the best way to find edge cases in WordPress plugin testing?

Finding edge cases in WordPress plugin testing involves systematically analyzing specification documents for boundary conditions related to permissions, data, states, and integrations. This Skill automates that extraction process, cross-referencing business rules with user roles to ensure comprehensive coverage.

Can I use wp-env with Playwright for automated WordPress test generation?

Yes, you can use wp-env with Playwright for automated WordPress test generation. This Skill produces executable Playwright tests designed for admin, frontend, and integration layers, specifically leveraging the wp-env environment to validate features across different user roles and states.

How do I create a test matrix for WordPress user permissions and roles?

To create a test matrix for WordPress user permissions, parse your specification documents to extract features and business rules, then cross-reference them with user roles like guest, subscriber, and admin. This Skill automatically plans coverage for scenarios where permissions are unexpectedly revoked or granted.

Does automated E2E test generation cover integration layers in WordPress?

Automated E2E test generation covers integration layers in WordPress by analyzing specification documents to identify integration boundaries. This Skill generates Playwright tests that validate how different components interact, ensuring that data and state transitions are thoroughly tested.

What limitations exist when generating tests from specification documents?

When generating tests from specification documents, the primary limitation is the quality and completeness of the input spec. If the specification lacks detailed business rules or user role definitions, the generated Playwright tests may miss critical edge cases related to permissions, data, and state boundaries.