Skill Tracer
Skills › Knowledge Work Plugins › testing-strategy

testing-strategy

skill · 33 lines · Apache-2.0 · engineering/skills/testing-strategy/SKILL.md

The facts

Its 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.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

The agent picks this skill when someone asks how to approach testing — a test strategy, a test plan, or which tests are needed for a feature or system. It is chosen from the description alone, which names testing approaches, coverage, and test architecture as its territory.

Things a person might say (the model's guesses)

  • “How should we test the new payments API?”
  • “Write a test plan for the checkout flow.”
  • “What tests do we need before we ship this?”

A model's summary of when it is used.

A model's reading

Licence

Apache-2.0, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

The text

Open on GitHub
1---
2name: testing-strategy
3description: 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.
4---
5
6# Testing Strategy
7
8Design effective testing strategies balancing coverage, speed, and maintenance.
9

Testing Strategy

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

Raw lines 1 to 9
10## Testing Pyramid
12```
13 / E2E \ Few, slow, high confidence
14 / Integration \ Some, medium speed
15 / Unit Tests \ Many, fast, focused
16```

Testing Pyramid

        /  E2E  \         Few, slow, high confidence
       / Integration \     Some, medium speed
      /    Unit Tests  \   Many, fast, focused
Raw lines 10 to 17
18## Strategy by Component Type
20- **API endpoints**: Unit tests for business logic, integration tests for HTTP layer, contract tests for consumers
21- **Data pipelines**: Input validation, transformation correctness, idempotency tests
22- **Frontend**: Component tests, interaction tests, visual regression, accessibility
23- **Infrastructure**: Smoke tests, chaos engineering, load tests

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
Raw lines 18 to 24
25## What to Cover
27Focus on: business-critical paths, error handling, edge cases, security boundaries, data integrity.
29Skip: trivial getters/setters, framework code, one-off scripts.

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.

Raw lines 25 to 30
31## Output
33Produce a test plan with: what to test, test type for each area, coverage targets, and example test cases. Identify gaps in existing coverage.

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.

Raw lines 31 to 33

From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.