testing-strategy

Layered test plan sized to the change's risk profile.

Score 0(?)OfficialAll surfacesby AnthropicSource
Verified for:

Install

$ claude plugin install engineering

Skill becomes available as /testing-strategy

Best for

Greenfield features when you need a real plan before writing the first test.

About this skill

Design test strategies and test plans — coverage, layering (unit/integration/E2E), test architecture.

TestingStrategyCoverage

Score breakdown

Score breakdown

rubric 1.0
Install count
0/20
Provenance
15/15
GitHub stars
0/15
Recency
8.5/10
Compatibility
8/10
Documentation depth
6.5/10
Install ergonomics
7/10
License
5/5
Verification freshness
5/5

Composite 0–100 score derived from 9 verifiable signals. See the rubric →

Deterministic web control. ref-based clicks/fills, no flaky selectors, parallel sessions.

BrowserAutomationAction-taking
Code

Test local webapps with Playwright. Generation, run, report — end-to-end.

PlaywrightE2ETesting
Code

Playwright patterns: clicks, fills, waits, retries. The do-it-right defaults.

PlaywrightAutomation
Code

Skill FAQ

About testing-strategy

What is the testing-strategy skill?

Design test strategies and test plans — coverage, layering (unit/integration/E2E), test architecture.

Which agents does testing-strategy work with?

Claude Code, Cursor, Codex CLI, Antigravity IDE.

How do I install testing-strategy?

Run `claude plugin install engineering` for Claude Code. See the install panel for per-agent commands.

Is testing-strategy free to use?

Yes — testing-strategy is open source (MIT).

Who maintains testing-strategy?

testing-strategy is published by Anthropic and was last updated on 2026-05-15.

What is testing-strategy best for?

Greenfield features when you need a real plan before writing the first test.