Wp Test Strategy logo

Wp Test Strategy

Community
jorgerosal
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.

Overview

Publisherjorgerosal
Repositorywordpress-skills
Skill namewp-test-strategy
Stars
113
Forks
13
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by jorgerosal on GitHub. Read the source before you install it.

Installation

Install the Wp Test Strategy AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/jorgerosal/wordpress-skills/tree/main/claude-skills/wp-test-strategy
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
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
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Wp Test Strategy in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Wp Test Strategy on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Wp Test Strategy is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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
    • What can be skipped or covered indirectly

Test Selection Heuristics

Unit Tests

Use for:

  • Pure transformation logic
  • Small helpers
  • Formatting and parsing logic
  • Validation rules decoupled from WP runtime

Integration Tests

Use for:

  • Hooks and filters
  • Option/meta persistence
  • REST endpoints
  • Custom queries
  • Role/capability behavior

E2E or Browser Tests

Use for:

  • Block editor flows
  • Admin forms with JS behavior
  • Checkout, cart, and frontend interactions
  • Accessibility-sensitive interaction flows

Search Patterns for Quick Detection (TST-21)

Use these rg commands to understand current test coverage and likely gaps.

Coverage Discovery

bash
# Test directories and files
rg -n "class .*Test|extends .*TestCase|describe\\(|test\\(" . -g '*.{php,js,jsx,ts,tsx}'

# PHPUnit config or bootstrap
rg -n "phpunit|tests/bootstrap|WP_UnitTestCase" .

# Playwright or E2E indicators
rg -n "playwright|@wordpress/e2e-test-utils|page\.goto|test\\(" . -g '*.{js,ts}'

Gap Signals

bash
# High-risk surfaces with no obvious tests nearby
rg -n "register_rest_route|add_action|add_filter|wp_ajax_|admin_post_|dbDelta|WC_" . -g '*.php'

# Block editor files
rg -n "block.json|edit\\(|save\\(|registerBlockType" . -g '*.{json,js,jsx}'

Reference Files

  • references/test-layer-guide.md - Choosing unit vs integration vs E2E coverage in WordPress projects
  • references/wordpress-test-scenarios.md - Recommended test scenarios for plugins, blocks, themes, REST APIs, and WooCommerce

Output Format (TST-23)

When reporting, organize by:

  1. Surface area under review
  2. Recommended test types
  3. Highest-priority missing coverage
  4. Nice-to-have coverage

If the existing tests are already sufficient, say that clearly and mention any residual risk or missing edge-case coverage.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Wp Test Strategy AI 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.

Why use Wp Test Strategy on TypingMind?

Because you install it once and use it with any model. Wp Test Strategy is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Wp Test Strategy in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jorgerosal/wordpress-skills/tree/main/claude-skills/wp-test-strategy. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Wp Test Strategy?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Wp Test Strategy?

As many as you like. As long as a model supports skills, you can use Wp Test Strategy with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Wp Test Strategy AI skill free?

Yes. It is published on GitHub by jorgerosal under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇