testing-plugin
v3.19.7Test execution, TDD workflow, testing strategies, and quality analysis
By Lauri GatesLicense: MIT58 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 17 skill or MCP entries
- Source updated
- Sep 15, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install testing-plugin for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install testing-plugin@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/laurigates/claude-pluginsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is testing-plugin/.
Plugin files
├── .claude-plugin/plugin.json├── skills/mutation-testing/SKILL.md├── skills/odiff-image-diffing/SKILL.md├── skills/playwright-cli/SKILL.md├── skills/playwright-testing/SKILL.md├── skills/property-based-testing/SKILL.md├── skills/test-analyze/SKILL.md├── skills/test-consult/SKILL.md├── skills/test-focus/SKILL.md├── skills/test-full/SKILL.md├── skills/test-quality-analysis/SKILL.md├── skills/test-quick/SKILL.md├── skills/test-report/SKILL.md├── skills/test-run/SKILL.md├── skills/test-setup/SKILL.md├── skills/test-strategy-review/SKILL.md├── skills/test-tier-selection/SKILL.md└── skills/vitest-testing/SKILL.md
Included Skills17
Mutation testing with Stryker (TS/JS) and mutmut (Python). Use when finding weak tests that pass on mutated code, or improving test quality through mutation analysis.
odiff pixel-by-pixel image diffing. Use when comparing screenshots, detecting visual regressions, diffing before/after PNGs, asserting golden images.
Playwright CLI browser automation — navigate, screenshot, fill forms, click. Use when automating browser tasks from the shell; 4-10x more token-efficient than Playwright MCP.
Playwright E2E testing — cross-browser, visual regression, API testing, mobile emulation. Use when writing E2E tests or setting up automated UI testing for web apps.
Property-based testing with fast-check (TS/JS) and Hypothesis (Python). Use when generating test data, finding edge cases, testing properties, or writing QuickCheck-style tests.
Analyze test results and create a fix plan with subagents. Use when triaging failing tests, analyzing JUnit XML, planning fixes for accessibility/security, or categorizing flaky/E2E failures.
Consult the test-architecture agent for strategy decisions. Use when asking about coverage gaps, test pyramid, framework selection, flaky-test remediation, or how to test X.
One test file, fail-fast — Playwright, Vitest, Jest, pytest, cargo, go test. Use when running a single spec file, headed/debug mode, or serial single-worker WebGL tests.
Every tier in pyramid order — unit, then integration, then E2E. Use when running all tests before a PR or commit, or generating a coverage report.
Detect test smells, overmocking, flaky tests, and coverage issues. Use when reviewing tests, improving test quality, or analyzing test effectiveness and reliability.
Unit tier only — skips slow, integration, and E2E tests for sub-30s feedback. Use when checking units after a change, running tests affected since the last commit, or unit watch mode.
Cached results from the last test run, no re-run — pass/fail counts, existing coverage report, history, flaky tests. Use when asked for current test status or standup health.
Run the project's tests — auto-detects pytest, vitest, jest, cargo, go test; whole suite or a name pattern. Use when asked to run the tests and no tier, single file, or fix cycle is named.
Configure testing infrastructure with CI/CD. Use when setting up tests, scaffolding test dirs, adding pre-commit hooks, GitHub Actions workflows, Codecov, or coverage badges.
Evaluate whether a test suite actually tests what it aims to, using an adversarial pass plus a tests-hidden cold read, then verify every finding against the code. Use when a suite is green but you doubt it would catch a real regression.
Decide which test tier a change needs — unit, integration, or E2E — from its scope; runs nothing itself. Use when deciding how much of the suite to run after a change.
Vitest test runner — Vite-native, ESM, watch/UI mode, coverage, mocking, snapshots. Use when setting up tests for Vite projects, migrating from Jest, or needing fast execution.
Plugin manifests1
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "testing-plugin",
"version": "3.19.7",
"description": "Test execution, TDD workflow, testing strategies, and quality analysis",
"author": {
"name": "Lauri Gates"
},
"repository": "https://github.com/laurigates/claude-plugins",
"license": "MIT",
"keywords": [
"testing",
"tdd",
"test-driven-development",
"pytest",
"vitest",
"coverage",
"test-runner",
"playwright",
"playwright-cli",
"browser-automation",
"odiff",
"image-diff",
"visual-regression"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[testing-plugin on Agent Plugins Marketplace](https://pluginsmp.com/plugins/testing-plugin)