Write, extend, or debug PHPUnit application tests for this WordPress plugin. Use this skill whenever tests are involved — adding a test for a new feature, testing hook or filter behavior, testing WordPress data operations with factories, or when asked to "add a test", "write tests", "test this function", or "verify this behavior with a test". This skill is opinionated about the project's wp-env-based setup and supersedes any generic PHPUnit guidance. --- # Application Testing Tests run exclusively inside the `wp-env` test container. The bootstrap and PHPUnit config are pre-wired. Do not modify `tests/bootstrap.php` or `phpunit.xml.dist`. The plugin is already loaded when tests run — no manual require needed. For full reference including common patterns, plugin dependencies, and CI details, read `references/testing.mdx`. ## Running the test suite
How to set up comprehensive logging and artifact extraction for Playwright e2e test suites. Use this skill when creating new e2e test suites, setting up Playwright from scratch, implementing BaseContext logging infrastructure, configuring test failure diagnostics, or adding custom test context logging. Essential for debugging e2e test failures with console logs, network logs, page errors, and Playwright artifacts (screenshots, videos, traces).
Generate and run end-to-end tests with Playwright. Creates test journeys, runs tests, captures screenshots/videos/traces, and uploads artifacts.
- 📄 emergence-config.json
- 📄 eval_queries.json
- 📄 lifecycle.json
Reviews existing test suites for coverage gaps, quality, and rigor; identifies weak or missing tests and guides fixes to reach a target coverage threshold. Use when asked to "review unit tests", "fix unit tests", "check test coverage", "audit tests", "improve test suite", or ensure coverage at end of an initiative or during maintenance. Do NOT use when the user asks to write tests from scratch for new, untested code.
QA scenario executor for {{project_name}}. Reads JSON test scenarios, replays them step-by-step on a connected device via mobile-mcp, captures screenshots, validates against reference baselines, and produces pass/fail result reports. Use when asked to execute, run, validate, or verify test scenarios.
Use when generating tests for backend code (Express routes, MongoDB models, Node services) - analyzes file type, detects test framework from package.json, generates comprehensive tests with setup/teardown and edge case coverage
Add support for a new AI coding tool to AgentSync's sync engine. USE WHEN adding a new tool, integrating a new AI assistant, or asked to support a new IDE/editor. --- # Add New Tool Support Add a new AI coding tool to AgentSync so `agentsync sync` distributes instructions to it. ## Steps 1. **Study an existing tool config** — Read `.ai/src/tools/claude.yaml` or `.ai/src/tools/cursor.yaml` for the pattern. 2. **Create the tool YAML** — Copy `.ai/src/tools/_TEMPLATE.yaml` to `.ai/src/tools/<tool>.yaml`. 3. **Configure targets** — Define where each content type goes: - `agents` → main instructions file - `rules` → rules directory or merged file - `skills` → skills directory (if supported) - `commands` → commands directory (if supported) - `subagents` → agents directory (if supported) - `settings` / `mcp` → tool-specific config files 4. **Handle format differences** — Check if the tool needs: - `.mdc` extension instead of `.md` (Cursor) - Frontmatter wrapping (`alwaysApply: true` for Cursor rules) - Inline skill/rule merging into agents file (`inline_into_agents: true`) - `00-context.md` pattern for AGENTS.md content in rules dir - TOML format for agents (Codex) 5. **Add sync logic** — If the tool needs custom transformation, add a handler in `lib/sync.sh` (look for the `sync_tool` function and existing tool-specific blocks). 6. **Add to `lib/templates/tools/`** — Create a default YAML config. 7. **Write tests** — Add assertions in: - `tests/sync.bats` — verify output files exist - `tests/sync_options.bats` — verify `--only`/`--skip` filtering - `tests/check.bats` — verify `agentsync check` detects drift 8. **Test on all platforms** — Run `bats tests/sync.bats` locally, verify CI passes. ## Gotchas - Every tool has quirks. Read the tool's docs for where it expects instruction files. - Some tools share output paths (e.g., Copilot uses `.github/`). Check for collisions with existing tools. - The custom YAML parser doesn't support arrays or multiline YAML blocks — keep too
Evaluate Python test suite quality using mutmut to introduce code mutations and verify tests catch them. Use for mutation testing, test quality assessment, mutant detection, and test effectiveness analysis.
- 📁 assets/
- 📁 references/
- 📁 scripts/
- 📄 checkpoints.yaml
- 📄 SKILL.md
Use when setting up DDEV for TYPO3 extension development, testing across multiple TYPO3 versions (11.5/12.4/13.4/14.0), configuring local dev environments, or multi-version testing. Also triggers on: ddev start, ddev config, local development, docker environment, PHP version management.
- 📁 references/
- 📁 scripts/
- 📁 templates/
- 📄 SKILL.md
Comprehensive TeaPie framework expertise for API integration testing. Use when: (1) Working with TeaPie projects, API testing, .http files, .tp files, C# test scripts (.csx), test collections, directives, variables, functions, authentication, retrying, (2) Creating and scaffolding test cases using `teapie generate`, renumbering tests, initializing TeaPie projects, (3) Running tests with `teapie test`, finding tests for API endpoints, debugging test failures, generating reports, (4) Analyzing .teapie folder structure, discovering custom functions/directives/auth providers registered in init.csx, understanding project-specific configurations, or (5) When users need guidance on TeaPie CLI commands, test structure, framework capabilities, or test organization.
- 📁 references/
- 📁 resources/
- 📄 SKILL.md
write and run eval tests, and iterate on failures.
