Wp Test Strategy

WordPress testing strategy and review guidance. Use when planning or reviewing PHPUnit coverage, integration tests, block tests, e2e tests, Playwright flows, WooCommerce test coverage, fixture design, or when user mentions "test strategy", "WordPress tests", "PHPUnit", "integration tests", "Playwright", "e2e", "test coverage", "testing plan", or "regression tests". Helps decide what to test, how deeply to test, and where to focus coverage in WordPress plugins, themes, blocks, and WooCommerce extensions.

116 stars 13 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jorgerosal/wordpress-skills --skill wp-test-strategy
Manual install
git clone --depth 1 https://github.com/jorgerosal/wordpress-skills.git /tmp/wordpress-skills
mkdir -p ~/.claude/skills
cp -r /tmp/wordpress-skills/claude-skills/wp-test-strategy ~/.claude/skills/wp-test-strategy

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# WordPress Test Strategy Skill

## Overview

Systematic testing strategy guidance for WordPress projects. **Core principle:** Test depth should match risk, and the test pyramid should reflect the WordPress surface area involved. Review covers unit tests, WordPress integration tests, REST endpoint tests, block tests, browser or E2E flows, WooCommerce regressions, fixtures, and release-risk prioritization.

## When to Use

**Use when:**
- Deciding what tests to add for a feature or fix
- Reviewing missing coverage in a plugin or theme
- Planning regression tests before release
- Choosing between unit, integration, and E2E coverage
- Mapping block, REST, admin, or WooCommerce behavior to tests

**Don't use for:**
- Code review that does not involve testing decisions
- CI system debugging only
- Performance benchmarking alone

## Code Review Workflow

1. **Identify the change surface**
   - Pure PHP logic
   - WordPress integration behavior
   - REST or AJAX flow
   - Block editor behavior
   - Admin screen workflow
   - WooCommerce order/cart/checkout behavior

2. **Map the risk**
   - User-facing breakage
   - Data corruption or migration risk
   - Auth/security-sensitive flow
   - Browser interaction complexity

3. **Choose test depth**
   - Unit tests for isolated logic
   - Integration tests for WordPress APIs and DB state
   - E2E tests for UI workflows or editor interactions

4. **Report recommendations**
   - What should be tested
   - What level of test is appropriate
Read the full skill on GitHub

Details

Skill name
wp-test-strategy
Path
claude-skills/wp-test-strategy/SKILL.md
License
MIT
Repo updated
7 June 2026

FAQ

What does the Wp Test Strategy skill do?

WordPress testing strategy and review guidance. Use when planning or reviewing PHPUnit coverage, integration tests, block tests, e2e tests, Playwright flows, WooCommerce test coverage, fixture design, or when user mentions "test strategy", "WordPress tests", "PHPUnit", "integration tests", "Playwright", "e2e", "test coverage", "testing plan", or "regression tests". Helps decide what to test, how deeply to test, and where to focus coverage in WordPress plugins, themes, blocks, and WooCommerce extensions.

How do I install the Wp Test Strategy skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jorgerosal/wordpress-skills --skill wp-test-strategy. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Wp Test Strategy popular?

It lives in jorgerosal/wordpress-skills, which has 116 GitHub stars and 13 forks.

Related skills

Wp Accessibility Review

116

jorgerosal/wordpress-skills

WordPress accessibility review for themes, blocks, plugins, and admin interfaces. Use when reviewing keyboard navigation, focus behavior, semantic HTML, ARIA usage, form labeling, screen-reader support, contrast-related implementation issues, or when user mentions "accessibility review", "a11y", "keyboard navigation", "focus management", "screen reader", "ARIA", "semantic HTML", "accessible form", or "accessible block". Detects implementation-level accessibility issues in frontend output, block markup, admin screens, and interactive UI behavior.

Frontend & Design13

Wp Accessibility Review

116

jorgerosal/wordpress-skills

WordPress accessibility review for Codex. Use when reviewing semantic HTML, keyboard access, focus behavior, form labels, ARIA usage, and accessible interaction patterns in themes, blocks, plugins, and admin screens.

Frontend & Design13

Wp Acf and Content Modeling

116

jorgerosal/wordpress-skills

WordPress ACF and content modeling review. Use when reviewing Advanced Custom Fields usage, field group architecture, CPT and taxonomy design, options pages, repeaters, flexible content, block-bound field groups, meta storage patterns, or when user mentions "ACF", "field groups", "flexible content", "repeater", "custom post type design", "taxonomy design", "content model", "relationship fields", "ACF JSON", "options page", or "meta query performance". Detects schema drift, weak content modeling, brittle field naming, and performance issues in meta-heavy WordPress builds.

AI, LLMs & Agents13

Wp Test Strategy

116

jorgerosal/wordpress-skills

WordPress test strategy guidance for Codex. Use when deciding what to test, how deeply to test it, and which mix of unit, integration, and E2E coverage fits a WordPress change.

Testing & QA13

Testing Python Libraries

115

wdm0006/python-skills

Designs and implements pytest test suites for Python libraries with fixtures, parametrization, mocking, Hypothesis property-based testing, and CI configuration. Use when creating tests, improving coverage, setting up testing infrastructure, or implementing property-based testing.

Testing & QA18

Earnings QA Analysis

132

OctagonAI/skills

Analyze the Q&A section of earnings call transcripts for strategic insights, analyst concerns, and management responses on key topics.

Testing & QA14

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.