feature-test

Generates and runs Playwright regression tests from git branch diffs of WordPress plugins.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/nahidthenh/wpsp-docker-e2e --skill feature-test-nahidthenh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-test
Source: https://github.com/nahidthenh/wpsp-docker-e2e/tree/main/.claude/skills/feature-test
Command: npx skills add https://github.com/nahidthenh/wpsp-docker-e2e --skill feature-test-nahidthenh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing a feature branch and writing end-to-end tests for every change is slow and error-prone. This Skill automates the loop: it diffs a branch against master in the SchedulePress free and pro plugin repos, drafts Playwright test cases for your approval, writes them into the regression suite, runs them, and reports pass/fail results. ## Core Features & Use Cases - Branch Diff Analysis: Resolves plugin paths from .env, locates the branch in free and pro repos, and diffs it against the default base branch while excluding lock files and minified assets. - Review-Gated Test Authoring: Proposes a structured test plan (file placement, describe blocks, rationale) and waits for your approval before writing any Playwright/TypeScript spec files. - Execution and Reporting: Runs only the new or modified spec via Playwright (starting Docker containers if needed) and produces a structured report with per-test status, failure details, and a merge recommendation. - Use Case: A developer pushes fix/calendar-timezone to the SchedulePress repo. Run the skill with that branch name to get diff-based test cases covering the timezone fix, executed against the local Docker WordPress environment, with a merge-safety summary. ## Quick Start Ask the assistant to run the feature-test skill on branch fix/calendar-timezone and include the pro repo if the change spans both plugins.

Frequently Asked Questions about feature-test

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

FAQPage Schema
How do I generate Playwright tests from a git branch diff?

Invoke the feature-test skill with the branch name, and it diffs the branch against master in the plugin repos, proposes test cases for approval, writes the Playwright spec file, and runs it. Use the --pro flag when the change also affects the pro plugin repo.

How do I test WordPress plugin changes end-to-end before merging?

Run the branch through this skill, which executes Playwright tests against a local Docker WordPress environment at localhost:8080. It reports per-test pass/fail status and gives a merge recommendation based on the results.

Does the skill support testing both free and pro plugin repos?

Yes, it always checks the free repo and silently checks the pro repo for the same branch. If the branch exists in pro, it is included automatically; the --pro flag forces inclusion and warns if the branch is missing there.

What happens if the Docker containers are not running when tests execute?

The skill detects this and starts the environment with docker compose up -d, waits briefly, then runs the Playwright spec. No manual container management is required before invoking the test run.

Where are the generated regression test files placed?

Tests are appended to an existing spec file if the change touches a covered area, otherwise a new numbered file is created in tests/regression/ using the next available NN prefix. Related tests for one branch are never split across multiple files.