Skills anthropics knowledge-work-plugins

testing-strategy

Use it when:: You ask how to test something, what tests you need, or for a test plan.
You get:: A test plan: what to test, the test type for each area, coverage targets, example test cases and gaps in existing coverage.
Starts from:: The testing pyramid: many fast unit tests, some integration tests and a few slow end-to-end tests.
By component:: API endpoints, data pipelines, frontends and infrastructure each get their own mix, from contract tests to chaos and load tests.
Part of:: The engineering plugin of Anthropic's knowledge-work plugins.

TL;DR

A one-page testing reference from the engineering plugin of Anthropic's knowledge-work plugins. It starts from the testing pyramid: many fast, focused unit tests, some integration tests and a few slow, high-confidence end-to-end tests. It then suggests a mix by component. API endpoints get unit tests for business logic, integration tests for the HTTP layer and contract tests for their consumers; data pipelines get input validation, transformation and idempotency tests; frontends get component, interaction, visual regression and accessibility tests; infrastructure gets smoke tests, chaos engineering and load tests. Tests should cover business-critical paths, error handling, edge cases, security boundaries and data integrity, and skip trivial getters and setters, framework code and one-off scripts. The result is a test plan listing what to test, the type of test for each area, coverage targets and example test cases, with the gaps in current coverage. It's short guidance with no step-by-step method.

Summarizes the skill at ab4cb1c.

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill testing-strategy

skills.sh page Source on GitHub All skills from anthropics/knowledge-work-plugins

Total Downloads: 6,700 on skills.sh, Nov 9, 2026
Repo stars: 35,234 anthropics/knowledge-work-plugins
First seen: Feb 24, 2026 on skills.sh

Weekly Downloads

111

0% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	111
Sep 28	79
Oct 5	59
Oct 12	72
Oct 19	108
Oct 26	136
Nov 2	102
Nov 9	111

Category	category:debugging category:software-engineering Find root causes, review code and test what you built. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type	type:guidelines Knowledge and rules the agent applies while it works: best practices, design principles, API references.
Effect	effect:none Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs	needs:none Instructions only. Works in any agent that supports skills.
Publisher	by:official A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics	testing planning

SKILL.md

From anthropics/knowledge-work-plugins at ab4cb1c. Checked daily, last changed Nov 6, 2026.

Frontmatter

name: testing-strategy
description: Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.

Testing Strategy

Design effective testing strategies balancing coverage, speed, and maintenance.

Testing Pyramid

        /  E2E  \         Few, slow, high confidence
       / Integration \     Some, medium speed
      /    Unit Tests  \   Many, fast, focused

Strategy by Component Type

API endpoints: Unit tests for business logic, integration tests for HTTP layer, contract tests for consumers
Data pipelines: Input validation, transformation correctness, idempotency tests
Frontend: Component tests, interaction tests, visual regression, accessibility
Infrastructure: Smoke tests, chaos engineering, load tests

What to Cover

Focus on: business-critical paths, error handling, edge cases, security boundaries, data integrity.

Skip: trivial getters/setters, framework code, one-off scripts.

Output

Produce a test plan with: what to test, test type for each area, coverage targets, and example test cases. Identify gaps in existing coverage.