npm - claude-plugin-wordpress-manager - Versions diffs - 1.5.0 → 1.7.1 - Mend

claude-plugin-wordpress-manager 1.5.0 → 1.7.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (68) hide show

package/.claude-plugin/plugin.json +2 -2
package/CHANGELOG.md +97 -0
package/README.md +27 -13
package/agents/wp-accessibility-auditor.md +206 -0
package/agents/wp-content-strategist.md +18 -0
package/agents/wp-deployment-engineer.md +34 -2
package/agents/wp-performance-optimizer.md +12 -0
package/agents/wp-security-auditor.md +20 -0
package/agents/wp-security-hardener.md +266 -0
package/agents/wp-site-manager.md +14 -0
package/agents/wp-test-engineer.md +207 -0
package/docs/guides/INDEX.md +46 -0
package/docs/guides/wp-blog.md +590 -0
package/docs/guides/wp-design-system.md +976 -0
package/docs/guides/wp-ecommerce.md +786 -0
package/docs/guides/wp-landing-page.md +762 -0
package/docs/guides/wp-portfolio.md +713 -0
package/docs/plans/2026-02-27-design-system-guide-design.md +30 -0
package/docs/plans/2026-02-27-site-type-guides-design.md +44 -0
package/package.json +2 -2
package/skills/wordpress-router/references/decision-tree.md +12 -2
package/skills/wp-accessibility/SKILL.md +170 -0
package/skills/wp-accessibility/references/a11y-audit-tools.md +248 -0
package/skills/wp-accessibility/references/a11y-testing.md +222 -0
package/skills/wp-accessibility/references/block-a11y.md +247 -0
package/skills/wp-accessibility/references/interactive-a11y.md +272 -0
package/skills/wp-accessibility/references/media-a11y.md +254 -0
package/skills/wp-accessibility/references/theme-a11y.md +309 -0
package/skills/wp-audit/SKILL.md +4 -0
package/skills/wp-block-development/SKILL.md +5 -0
package/skills/wp-block-themes/SKILL.md +4 -0
package/skills/wp-e2e-testing/SKILL.md +186 -0
package/skills/wp-e2e-testing/references/ci-integration.md +174 -0
package/skills/wp-e2e-testing/references/jest-wordpress.md +114 -0
package/skills/wp-e2e-testing/references/phpunit-wordpress.md +141 -0
package/skills/wp-e2e-testing/references/playwright-wordpress.md +108 -0
package/skills/wp-e2e-testing/references/test-data-generation.md +127 -0
package/skills/wp-e2e-testing/references/visual-regression.md +107 -0
package/skills/wp-e2e-testing/references/wp-env-setup.md +97 -0
package/skills/wp-e2e-testing/scripts/test_inspect.mjs +375 -0
package/skills/wp-headless/SKILL.md +168 -0
package/skills/wp-headless/references/api-layer-choice.md +160 -0
package/skills/wp-headless/references/cors-config.md +245 -0
package/skills/wp-headless/references/frontend-integration.md +331 -0
package/skills/wp-headless/references/headless-auth.md +286 -0
package/skills/wp-headless/references/webhooks.md +277 -0
package/skills/wp-headless/references/wpgraphql.md +331 -0
package/skills/wp-headless/scripts/headless_inspect.mjs +321 -0
package/skills/wp-i18n/SKILL.md +170 -0
package/skills/wp-i18n/references/js-i18n.md +201 -0
package/skills/wp-i18n/references/multilingual-setup.md +219 -0
package/skills/wp-i18n/references/php-i18n.md +196 -0
package/skills/wp-i18n/references/rtl-support.md +206 -0
package/skills/wp-i18n/references/translation-workflow.md +178 -0
package/skills/wp-i18n/references/wpcli-i18n.md +177 -0
package/skills/wp-i18n/scripts/i18n_inspect.mjs +330 -0
package/skills/wp-interactivity-api/SKILL.md +4 -0
package/skills/wp-plugin-development/SKILL.md +6 -0
package/skills/wp-rest-api/SKILL.md +4 -0
package/skills/wp-security/SKILL.md +179 -0
package/skills/wp-security/references/api-restriction.md +147 -0
package/skills/wp-security/references/authentication-hardening.md +105 -0
package/skills/wp-security/references/filesystem-hardening.md +105 -0
package/skills/wp-security/references/http-headers.md +105 -0
package/skills/wp-security/references/incident-response.md +144 -0
package/skills/wp-security/references/user-capabilities.md +115 -0
package/skills/wp-security/references/wp-config-security.md +129 -0
package/skills/wp-security/scripts/security_inspect.mjs +393 -0

package/skills/wp-accessibility/references/theme-a11y.md ADDED Viewed

@@ -0,0 +1,309 @@
+# Theme Accessibility
+Use this file when building accessible WordPress themes and achieving `accessibility-ready` tag compliance.
+## accessibility-ready tag requirements
+WordPress.org requires these for the `accessibility-ready` tag:
+1. **Skip links** — must be the first focusable element
+2. **Keyboard navigation** — all interactive elements reachable and operable
+3. **Contrast ratios** — text meets WCAG 2.1 AA (4.5:1 normal, 3:1 large)
+4. **Resize text** — content usable at 200% zoom
+5. **Form labels** — all inputs have associated labels
+6. **Image alt text** — all images have alt attributes (decorative = `alt=""`)
+7. **Visible focus** — focus indicators on all interactive elements
+8. **Landmarks** — proper use of HTML5 landmark elements
+9. **No autoplay** — media must not autoplay with sound
+## Landmarks and page structure
+```html
+<body <?php body_class(); ?>>
+    <?php wp_body_open(); ?>
+    <a class="skip-link screen-reader-text" href="#primary">
+        <?php esc_html_e('Skip to content', 'my-theme'); ?>
+    </a>
+    <header id="masthead" role="banner">
+        <nav id="site-navigation" role="navigation"
+             aria-label="<?php esc_attr_e('Primary Menu', 'my-theme'); ?>">
+            <?php wp_nav_menu(['theme_location' => 'primary']); ?>
+        </nav>
+    </header>
+    <main id="primary" role="main">
+        <!-- page content -->
+    </main>
+    <aside id="sidebar" role="complementary"
+           aria-label="<?php esc_attr_e('Sidebar', 'my-theme'); ?>">
+        <?php dynamic_sidebar('sidebar-1'); ?>
+    </aside>
+    <footer id="colophon" role="contentinfo">
+        <!-- footer content -->
+    </footer>
+</body>
+```
+## Skip link CSS
+```css
+.skip-link {
+    position: absolute;
+    top: -100%;
+    left: 0;
+    z-index: 999999;
+    padding: 0.5rem 1rem;
+    background: #000;
+    color: #fff;
+    text-decoration: none;
+    font-size: 1rem;
+}
+.skip-link:focus {
+    top: 0;
+    clip: auto;
+    clip-path: none;
+    width: auto;
+    height: auto;
+}
+```
+## Focus indicators
+```css
+/* Visible focus for all interactive elements */
+a:focus,
+button:focus,
+input:focus,
+select:focus,
+textarea:focus,
+[tabindex]:focus {
+    outline: 2px solid var(--wp--preset--color--primary, #0073aa);
+    outline-offset: 2px;
+}
+/* Remove default only if replacing with custom indicator */
+a:focus-visible {
+    outline: 3px solid #0073aa;
+    outline-offset: 2px;
+    border-radius: 2px;
+}
+```
+Never use `outline: none` without providing an alternative visible focus indicator.
+## Navigation menus
+### Menu walker with ARIA
+```php
+// In header.php or navigation template
+wp_nav_menu([
+    'theme_location' => 'primary',
+    'container'      => 'nav',
+    'container_class' => 'main-navigation',
+    'container_id'    => 'primary-menu',
+    'items_wrap'     => '<ul id="%1$s" class="%2$s" role="menubar">%3$s</ul>',
+]);
+```
+### Dropdown submenus
+```js
+// Accessible submenu toggle
+document.querySelectorAll('.menu-item-has-children > a').forEach((link) => {
+    const submenu = link.nextElementSibling;
+    const toggle = document.createElement('button');
+    toggle.className = 'submenu-toggle';
+    toggle.setAttribute('aria-expanded', 'false');
+    toggle.setAttribute('aria-label',
+        link.textContent.trim() + ' submenu');
+    toggle.innerHTML = '<span class="screen-reader-text">Toggle submenu</span>';
+    toggle.addEventListener('click', () => {
+        const expanded = toggle.getAttribute('aria-expanded') === 'true';
+        toggle.setAttribute('aria-expanded', String(!expanded));
+        submenu.hidden = expanded;
+    });
+    link.after(toggle);
+});
+```
+## Forms
+```html
+<!-- Every input needs a label -->
+<label for="search-input">
+    <?php esc_html_e('Search', 'my-theme'); ?>
+</label>
+<input type="search" id="search-input" name="s"
+       placeholder="<?php esc_attr_e('Search...', 'my-theme'); ?>">
+<!-- Group related fields -->
+<fieldset>
+    <legend><?php esc_html_e('Contact Information', 'my-theme'); ?></legend>
+    <label for="name"><?php esc_html_e('Name', 'my-theme'); ?></label>
+    <input type="text" id="name" name="name" required
+           aria-required="true">
+    <label for="email"><?php esc_html_e('Email', 'my-theme'); ?></label>
+    <input type="email" id="email" name="email" required
+           aria-required="true">
+</fieldset>
+<!-- Error messages -->
+<input type="email" id="email" name="email"
+       aria-describedby="email-error" aria-invalid="true">
+<p id="email-error" class="form-error" role="alert">
+    <?php esc_html_e('Please enter a valid email address.', 'my-theme'); ?>
+</p>
+```
+## Images in themes
+```php
+<!-- Content images: meaningful alt -->
+<img src="<?php echo esc_url($image_url); ?>"
+     alt="<?php echo esc_attr($image_alt); ?>">
+<!-- Decorative images: empty alt -->
+<img src="decorative-border.png" alt="" role="presentation">
+<!-- Background images with text: ensure contrast or provide alt -->
+<div class="hero" style="background-image: url(hero.jpg);"
+     role="img" aria-label="<?php esc_attr_e('Mountain landscape', 'my-theme'); ?>">
+    <h1><?php esc_html_e('Welcome', 'my-theme'); ?></h1>
+</div>
+```
+### Post thumbnails
+```php
+// Theme support with alt text
+if (has_post_thumbnail()) {
+    the_post_thumbnail('large', [
+        'alt' => get_the_title(), // fallback if no alt set
+    ]);
+}
+```
+## Color and typography
+```css
+/* Ensure readable text sizes */
+body {
+    font-size: 1rem;    /* At least 16px */
+    line-height: 1.5;   /* WCAG recommends 1.5 for body text */
+}
+/* Respect user preferences */
+@media (prefers-reduced-motion: reduce) {
+    *,
+    *::before,
+    *::after {
+        animation-duration: 0.01ms !important;
+        transition-duration: 0.01ms !important;
+        scroll-behavior: auto !important;
+    }
+}
+@media (prefers-contrast: more) {
+    :root {
+        --text-color: #000;
+        --bg-color: #fff;
+        --link-color: #00008b;
+    }
+}
+```
+## Screen reader utilities
+```css
+/* WordPress core screen-reader-text class */
+.screen-reader-text {
+    border: 0;
+    clip: rect(1px, 1px, 1px, 1px);
+    clip-path: inset(50%);
+    height: 1px;
+    margin: -1px;
+    overflow: hidden;
+    padding: 0;
+    position: absolute !important;
+    width: 1px;
+    word-wrap: normal !important;
+}
+.screen-reader-text:focus {
+    background-color: #f1f1f1;
+    clip: auto !important;
+    clip-path: none;
+    display: block;
+    font-size: 0.875rem;
+    height: auto;
+    left: 5px;
+    line-height: normal;
+    padding: 15px 23px 14px;
+    text-decoration: none;
+    top: 5px;
+    width: auto;
+    z-index: 100000;
+}
+```
+## theme.json accessibility settings
+```json
+{
+    "settings": {
+        "color": {
+            "palette": [
+                {
+                    "slug": "primary",
+                    "color": "#0073aa",
+                    "name": "Primary"
+                },
+                {
+                    "slug": "foreground",
+                    "color": "#1e1e1e",
+                    "name": "Foreground"
+                },
+                {
+                    "slug": "background",
+                    "color": "#ffffff",
+                    "name": "Background"
+                }
+            ]
+        },
+        "typography": {
+            "fluid": true,
+            "fontSizes": [
+                { "slug": "small", "size": "0.875rem", "name": "Small" },
+                { "slug": "medium", "size": "1rem", "name": "Medium" },
+                { "slug": "large", "size": "1.25rem", "name": "Large" }
+            ]
+        }
+    }
+}
+```
+Ensure all palette color combinations meet WCAG AA contrast ratios.
+## Verification
+```bash
+# Test theme accessibility-ready requirements
+npx @axe-core/cli https://localhost:8888/ --tags wcag2a,wcag2aa
+# Check for missing alt attributes
+curl -s https://site.com/ | grep -oP '<img[^>]*>' | grep -v 'alt='
+# Check for skip link
+curl -s https://site.com/ | grep -i "skip"
+# Validate landmarks
+curl -s https://site.com/ | grep -cE "<(main|nav|header|footer|aside|section)"
+```

package/skills/wp-audit/SKILL.md CHANGED Viewed

@@ -112,3 +112,7 @@ Combine findings into a unified report with:
 - **`references/security-checklist.md`** - WordPress security audit checklist
 - **`references/performance-checklist.md`** - Performance analysis checklist
 - **`references/seo-checklist.md`** - SEO audit checklist
+## Related skills
+- `wp-security` — Deep security hardening, filesystem permissions, HTTP headers, incident response procedures

package/skills/wp-block-development/SKILL.md CHANGED Viewed

@@ -174,3 +174,8 @@ If you’re uncertain about upstream behavior/version support, consult canonical
 - WordPress Developer Resources (Block Editor Handbook, Theme Handbook, Plugin Handbook)
 - Gutenberg repo docs for bleeding-edge behaviors
+## Related skills
+- `wp-e2e-testing` — Playwright E2E tests, Jest unit tests for block JavaScript, wp-env test environments
+- `wp-accessibility` — Block ARIA patterns, keyboard navigation, color contrast checks

package/skills/wp-block-themes/SKILL.md CHANGED Viewed

@@ -116,3 +116,7 @@ Common issues:
 If upstream behavior is unclear, consult canonical docs:
 - Theme Handbook and Block Editor Handbook for `theme.json`, templates, patterns, and style variations.
+## Related skills
+- `wp-accessibility` — Theme accessibility-ready requirements, skip links, focus indicators, WCAG compliance

package/skills/wp-e2e-testing/SKILL.md ADDED Viewed

@@ -0,0 +1,186 @@
+---
+name: wp-e2e-testing
+description: "Use when setting up, writing, or debugging WordPress tests: E2E with Playwright, unit tests with PHPUnit, JavaScript tests with Jest, visual regression, test data generation, wp-env test environment, and CI pipeline integration."
+compatibility: "Targets WordPress 6.9+ (PHP 7.2.24+). Filesystem-based agent with bash + node. Some workflows require WP-CLI and Docker."
+version: 1.0.0
+source: "vinmor/wordpress-manager"
+---
+# WP E2E Testing
+## When to use
+Use this skill when the task involves WordPress testing workflows:
+- Setting up a test suite from scratch for a WordPress plugin, theme, or block
+- Writing E2E tests with Playwright against a running WordPress instance
+- Adding PHPUnit tests for PHP code (hooks, filters, REST endpoints, custom post types)
+- Writing Jest unit tests for JavaScript/React block code
+- Debugging test failures in CI or locally
+- Setting up a CI pipeline (GitHub Actions) for WordPress test automation
+- Adding visual regression testing to catch unintended UI changes
+- Generating test data and fixtures for reproducible test runs
+- Configuring wp-env as a Docker-based test environment
+## Inputs required
+- **Repo root**: current working directory or `--cwd` path
+- **Project kind**: plugin, theme, or block (auto-detected via `detect_wp_project.mjs`)
+- **Existing test setup**: which frameworks are already configured (auto-detected via `test_inspect.mjs`)
+- **CI platform**: GitHub Actions is the primary target; adaptable to others
+## Procedure
+### 0) Detect existing test setup
+Run the detection scripts to understand what is already in place:
+```bash
+node skills/wp-e2e-testing/scripts/test_inspect.mjs
+node skills/wp-project-triage/scripts/detect_wp_project.mjs
+```
+The `test_inspect.mjs` script outputs JSON with:
+- `frameworks` — which test frameworks are configured (Playwright, Jest, PHPUnit, visual regression)
+- `testEnvironment` — whether wp-env and Docker are available
+- `ci` — whether CI workflows exist and which platform
+- `summary` — boolean flags for quick decision-making
+Use this output to skip steps that are already complete and focus on gaps.
+### 1) Choose testing strategy by project kind
+Different WordPress project types need different testing approaches:
+| Project kind | E2E (Playwright) | Unit JS (Jest) | Unit PHP (PHPUnit) | Visual regression |
+|-------------|:-:|:-:|:-:|:-:|
+| Plugin (classic) | Optional | If has JS | Recommended | Optional |
+| Plugin (block) | Recommended | Recommended | Recommended | Recommended |
+| Theme (classic) | Optional | Rare | Optional | Recommended |
+| Theme (block/FSE) | Recommended | If has JS | Optional | Recommended |
+| Gutenberg contrib | Required | Required | Required | Required |
+**General rule**: if the project has a user-facing UI, add E2E tests. If it has PHP logic (hooks, filters, REST), add PHPUnit. If it has JS/React, add Jest. If appearance matters, add visual regression.
+### 2) Set up test environment (wp-env)
+wp-env provides a Docker-based WordPress instance purpose-built for testing. It spins up two environments: development (port 8888) and tests (port 8889).
+Key steps:
+1. Ensure Docker is running (`docker info`)
+2. Create or verify `.wp-env.json` in the project root
+3. Start the environment with `npx wp-env start`
+4. Verify with `npx wp-env run tests-cli wp option get siteurl`
+The tests environment is isolated and can be reset without affecting development data. PHPUnit runs inside the tests container. Playwright connects to the development or tests URL.
+Read: `references/wp-env-setup.md`
+### 3) E2E tests with Playwright
+WordPress provides `@wordpress/e2e-test-utils-playwright` which wraps Playwright with WordPress-specific utilities: authenticated admin sessions, block editor helpers, REST API seeding.
+Key steps:
+1. Install Playwright and WP utilities
+2. Configure `playwright.config.ts` with WordPress base URL
+3. Write tests using `admin`, `editor`, and `requestUtils` fixtures
+4. Run with `npx wp-scripts test-playwright` or `npx playwright test`
+Read: `references/playwright-wordpress.md`
+### 4) JavaScript unit tests with Jest
+`@wordpress/scripts` bundles a preconfigured Jest setup. It handles JSX/TSX transforms, WordPress global mocks, and module resolution.
+Key steps:
+1. Ensure `@wordpress/scripts` is a devDependency
+2. Add a `test-unit-js` script to package.json (or use the default)
+3. Create test files alongside source (`*.test.js`) or in `__tests__/`
+4. Mock WordPress globals (`wp`, `jQuery`) as needed
+5. Run with `npx wp-scripts test-unit-js`
+Read: `references/jest-wordpress.md`
+### 5) PHP unit tests with PHPUnit
+WordPress ships a PHPUnit test bootstrapper. The `wp scaffold plugin-tests` WP-CLI command generates the full scaffolding.
+Key steps:
+1. Scaffold test files with `wp scaffold plugin-tests my-plugin`
+2. Extend `WP_UnitTestCase` for WordPress-aware tests
+3. Use `set_up()` and `tear_down()` for test lifecycle
+4. Test hooks, filters, REST endpoints, and custom post types
+5. Run with `npx wp-env run tests-cli --env-cwd=wp-content/plugins/my-plugin phpunit`
+Read: `references/phpunit-wordpress.md`
+### 6) Visual regression testing
+Screenshot comparison catches unintended UI changes. Playwright's built-in `toHaveScreenshot()` matcher is the simplest approach for WordPress projects already using Playwright.
+Key steps:
+1. Add screenshot assertions to existing Playwright tests
+2. Generate baseline screenshots on the main branch
+3. Configure threshold tolerance for acceptable pixel differences
+4. Store baselines in the repository or as CI artifacts
+5. Review diffs on failure before updating baselines
+Read: `references/visual-regression.md`
+### 7) Test data and fixtures
+Reproducible tests need predictable data. WordPress provides factory methods for PHP tests and REST API utilities for E2E tests.
+Key steps:
+1. Use `self::factory()->post->create()` in PHPUnit tests
+2. Use `requestUtils.createPost()` in Playwright E2E tests
+3. Seed bulk data via WP-CLI (`wp post generate`)
+4. Clean up after each test to prevent state leakage
+Read: `references/test-data-generation.md`
+### 8) CI pipeline integration
+GitHub Actions is the standard CI platform for WordPress projects. A typical pipeline runs PHPUnit across a PHP version matrix, Jest for JS tests, and Playwright for E2E.
+Key steps:
+1. Create `.github/workflows/tests.yml`
+2. Add MySQL service container for PHPUnit
+3. Define a test matrix for PHP and WP version combinations
+4. Cache node_modules and Composer vendor
+5. Upload Playwright traces and screenshots as artifacts on failure
+Read: `references/ci-integration.md`
+## Verification
+After completing the setup, verify:
+- `npx wp-scripts test-unit-js` passes (if Jest tests exist)
+- `npx wp-env run tests-cli --env-cwd=wp-content/plugins/<plugin> phpunit` passes (if PHPUnit tests exist)
+- `npx wp-scripts test-playwright` passes (if E2E tests exist)
+- Visual regression baselines are generated and stored
+- CI workflow runs green on push and pull request events
+- Test coverage meets project threshold (aim for 80%+ on critical paths)
+## Failure modes / debugging
+- **wp-env fails to start**: check Docker is running (`docker info`), check port conflicts (`lsof -i :8888`), try `npx wp-env destroy` then `npx wp-env start`
+- **Playwright tests timeout**: increase `timeout` in `playwright.config.ts`, ensure wp-env is fully started before tests run, check `baseURL` matches the running instance
+- **PHPUnit "No tests executed"**: verify `phpunit.xml` points to the correct test directory, ensure test class extends `WP_UnitTestCase`, ensure method names start with `test_`
+- **Jest "Cannot find module"**: check `moduleNameMapper` in jest config, ensure `@wordpress/scripts` is installed, run `npm install` to refresh dependencies
+- **Visual regression false positives**: increase pixel threshold, mask dynamic elements (timestamps, ads), use consistent viewport sizes, disable animations in test config
+- **CI MySQL connection refused**: ensure the `mysql` service container is healthy before running PHPUnit, add a wait step or health check
+- **"Class WP_UnitTestCase not found"**: the test bootstrap is missing or the WordPress test library is not installed; re-run `bin/install-wp-tests.sh` or use wp-env which handles this automatically
+## Escalation
+- For Gutenberg-specific testing: https://developer.wordpress.org/block-editor/contributors/code/testing-overview/
+- For @wordpress/scripts: https://developer.wordpress.org/block-editor/reference-guides/packages/packages-scripts/
+- For wp-env: https://developer.wordpress.org/block-editor/reference-guides/packages/packages-env/
+- For Playwright WP utilities: https://developer.wordpress.org/block-editor/reference-guides/packages/packages-e2e-test-utils-playwright/
+- For PHPUnit with WordPress: https://make.wordpress.org/core/handbook/testing/automated-testing/phpunit/
+## Recommended Agent
+For hands-on test execution, debugging, and CI setup, use the **`wp-test-engineer`** agent.

package/skills/wp-e2e-testing/references/ci-integration.md ADDED Viewed

@@ -0,0 +1,174 @@
+# CI Pipeline Integration for WordPress Tests
+Use this file when setting up GitHub Actions (or similar CI) for WordPress test automation.
+## GitHub Actions workflow
+```yaml
+# .github/workflows/tests.yml
+name: Tests
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+jobs:
+  php-tests:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        php: ['8.1', '8.2', '8.3']
+        wp: ['6.8', '6.9']
+    services:
+      mysql:
+        image: mysql:8.0
+        env:
+          MYSQL_ROOT_PASSWORD: root
+          MYSQL_DATABASE: wordpress_test
+        ports: ['3306:3306']
+        options: >-
+          --health-cmd="mysqladmin ping"
+          --health-interval=10s
+          --health-timeout=5s
+          --health-retries=5
+    steps:
+      - uses: actions/checkout@v4
+      - name: Setup PHP
+        uses: shivammathur/setup-php@v2
+        with:
+          php-version: ${{ matrix.php }}
+          extensions: mysqli
+          coverage: xdebug
+      - name: Cache Composer
+        uses: actions/cache@v4
+        with:
+          path: vendor
+          key: composer-${{ hashFiles('composer.lock') }}
+      - name: Install dependencies
+        run: composer install --no-interaction
+      - name: Install WP test suite
+        run: bash bin/install-wp-tests.sh wordpress_test root root 127.0.0.1 ${{ matrix.wp }}
+      - name: Run PHPUnit
+        run: vendor/bin/phpunit
+  js-tests:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+      - name: Install dependencies
+        run: npm ci
+      - name: Run Jest
+        run: npx wp-scripts test-unit-js --ci --coverage
+  e2e-tests:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+      - name: Install dependencies
+        run: npm ci
+      - name: Install Playwright browsers
+        run: npx playwright install chromium --with-deps
+      - name: Start wp-env
+        run: npx wp-env start
+      - name: Run Playwright tests
+        run: npx wp-scripts test-playwright
+      - name: Upload artifacts on failure
+        uses: actions/upload-artifact@v4
+        if: failure()
+        with:
+          name: playwright-artifacts
+          path: artifacts/
+          retention-days: 7
+```
+## Caching strategies
+```yaml
+# Node modules
+- uses: actions/cache@v4
+  with:
+    path: ~/.npm
+    key: npm-${{ hashFiles('package-lock.json') }}
+# Playwright browsers
+- uses: actions/cache@v4
+  with:
+    path: ~/.cache/ms-playwright
+    key: playwright-${{ hashFiles('package-lock.json') }}
+# Docker images for wp-env
+- uses: ScribeMD/docker-cache@0.5.0
+  with:
+    key: docker-${{ hashFiles('.wp-env.json') }}
+```
+## Parallel test execution
+Split Playwright tests across multiple workers:
+```yaml
+e2e-tests:
+  strategy:
+    matrix:
+      shard: [1, 2, 3]
+  steps:
+    # ...
+    - run: npx playwright test --shard=${{ matrix.shard }}/3
+```
+## PHPUnit without wp-env (standalone)
+For projects that don't use wp-env, the `install-wp-tests.sh` script sets up the WP test suite:
+```bash
+bash bin/install-wp-tests.sh wordpress_test root root 127.0.0.1 latest true
+```
+Arguments: `db_name db_user db_pass db_host wp_version skip_db_create`
+## Conditional jobs
+Run expensive E2E tests only when relevant files change:
+```yaml
+e2e-tests:
+  if: |
+    contains(github.event.pull_request.labels.*.name, 'e2e') ||
+    github.ref == 'refs/heads/main'
+```
+## Best practices
+- Run PHPUnit with matrix strategy for PHP/WP version coverage
+- Cache aggressively (npm, Composer, Playwright browsers, Docker)
+- Upload test artifacts (traces, screenshots) on failure for debugging
+- Use `--ci` flag for Jest to disable interactive mode
+- Set reasonable timeouts to catch hanging tests early
+- Run lint/format checks as a separate job (fast fail)