test-strategy-template
Common template for test strategy, design principles, and coverage planning.
Install
mkdir -p .claude/skills/test-strategy-template && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14936" && unzip -o skill.zip -d .claude/skills/test-strategy-template && rm skill.zipInstalls to .claude/skills/test-strategy-template
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
テスト戦略の共通テンプレート。テストピラミッド定義・テストダブル選択基準・ テストデータ戦略・カバレッジ方針を提供する。 USE FOR: test strategy, test pyramid, test doubles selection. DO NOT USE FOR: test code generation (agents do that). WHEN: テスト戦略書を作成する、テストダブルの選択基準を参照する。Key capabilities
- →Define test pyramid ratios for Unit, Integration, and E2E tests
- →Establish criteria for selecting test doubles
- →Formulate strategies for managing test data
- →Set code coverage targets for different test types
- →Provide guidelines for test design principles
- →Centralize test strategy documentation
How it works
The skill provides a common template for test strategies, defining principles for test pyramids, test double selection, test data management, and coverage goals. It serves as a centralized reference for test design principles.
Inputs & outputs
When to use test-strategy-template
- →Design test strategy
- →Select test doubles
- →Define coverage policy
- →Plan test pyramids
About this skill
test-strategy-template
目的
テスト戦略書・テスト仕様書に共通する テスト設計の原則 を一元管理する。各 Agent は本 Skill を参照し、固有のテスト種別のみを Agent 側に記載する。
Non-goals
- テストコードの生成 — Dev-*-TestCoding 系 Agent が担当
- 個別テストケースの設計 — Arch-TDD-TestSpec Agent が担当
- CI/CD パイプラインへのテスト組み込み — Skill
github-actions-cicdまたは Dev-*-Deploy 系 Agent が担当
原則サマリー（詳細: references/test-design-principles.md）
- テストピラミッド: Unit Test 70-80% / Integration Test 15-20% / E2E Test 5-10%
- テストダブル選択: Azurite（Azure Storage）→ Testcontainers（DB/コンテナ）→ Mock/Stub（その他）の優先順位
- 実行環境: Unit / 実装コード向け TDD RED / TDD GREEN はローカル実行可能を既定とし、外部サービスを使う Integration / Post-deploy / E2E は環境変数・設定ファイルで接続先を注入する
- テストデータ: Faker（ランダム生成）/ シード管理（固定シード・再現可能）/ 本番データサニタイズ
- カバレッジ: Unit Test ビジネスロジック 80% 以上、変換ロジック 100% 目標
ガイド一覧（references/）
| ファイル | 内容 |
|---|---|
references/test-design-principles.md | §1 テストピラミッド定義、§2 テストダブル選択基準（依存パターン別推奨ツール・優先順位）、§3 テストデータ戦略（Faker/シード管理/本番サニタイズ・エッジケース）、§4 カバレッジ方針 |
入出力例
※ 以下は説明用の架空例です
例1（SVC-10 Azure Functions マイクロサービス）: Unit Test(pytest + unittest.mock) 75% / Integration Test(pytest + Testcontainers + WireMock) 20% / E2E Test 5%
例2（データフロー処理テストダブル設計）: Azure Blob Storage → Azurite（優先順位1）/ Cosmos DB → Testcontainers（優先順位2）/ 外部REST API → WireMock（優先順位3）
参照元
- P-06 の詳細は旧 work スナップショット由来のため、実行時には参照しない。
When not to use it
- →When generating test code
- →When designing individual test cases
- →When integrating tests into CI/CD pipelines
Limitations
- →Does not generate test code
- →Does not design individual test cases
- →Does not integrate tests into CI/CD pipelines
How it compares
This skill centralizes and standardizes test design principles across projects, offering a consistent framework for test strategy development, which is more efficient than creating ad-hoc strategies for each new project.
Compared to similar skills
test-strategy-template side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| test-strategy-template (this skill) | 0 | 2mo | No flags | Beginner |
| d365-technical-plan-designer | 0 | 3mo | No flags | Advanced |
| go-dev-guidelines | 14 | 9mo | No flags | Intermediate |
| nestjs-expert | 37 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by dahatake
View all by dahatake →You might also like
d365-technical-plan-designer
williamzhou1216
D365 技术设计与实施计划编排专家（把 spec 转成 plan）
go-dev-guidelines
jumppad-labs
This skill should be used when writing, refactoring, or testing Go code. It provides idiomatic Go development patterns, TDD-based workflows, project structure conventions, and testing best practices using testify/require and mockery. Activate this skill when creating new Go features, services, packages, tests, or when setting up new Go projects.
nestjs-expert
davila7
Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js authentication. Use PROACTIVELY for any Nest.js application issues including architecture decisions, testing strategies, performance optimization, or debugging complex dependency injection problems. If a specialized expert is a better fit, I will recommend switching and stop.
scale-game
mrgoonie
Test at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales
implement-feature
tddworks
Guide for implementing features in ClaudeBar following architecture-first design, TDD, rich domain models, and Swift 6.2 patterns. Use this skill when: (1) Adding new functionality to the app (2) Creating domain models that follow user's mental model (3) Building SwiftUI views that consume domain models directly (4) User asks "how do I implement X" or "add feature Y" (5) Implementing any feature that spans Domain, Infrastructure, and App layers
wiring
parcadei
Wiring Verification