testing-strategy
Comprehensive testing strategy using Vitest for unit/integration tests and Playwright for E2E tests with best practices and coverage targets
下記のコマンドをコピーしてターミナル(Mac/Linux)または PowerShell(Windows)に貼り付けてください。 ダウンロード → 解凍 → 配置まで全自動。
mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -L -o testing-strategy.zip https://jpskill.com/download/17336.zip && unzip -o testing-strategy.zip && rm testing-strategy.zip
$d = "$env:USERPROFILE\.claude\skills"; ni -Force -ItemType Directory $d | Out-Null; iwr https://jpskill.com/download/17336.zip -OutFile "$d\testing-strategy.zip"; Expand-Archive "$d\testing-strategy.zip" -DestinationPath $d -Force; ri "$d\testing-strategy.zip"
完了後、Claude Code を再起動 → 普通に「動画プロンプト作って」のように話しかけるだけで自動発動します。
💾 手動でダウンロードしたい(コマンドが難しい人向け)
- 1. 下の青いボタンを押して
testing-strategy.zipをダウンロード - 2. ZIPファイルをダブルクリックで解凍 →
testing-strategyフォルダができる - 3. そのフォルダを
C:\Users\あなたの名前\.claude\skills\(Win)または~/.claude/skills/(Mac)へ移動 - 4. Claude Code を再起動
⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。
🎯 このSkillでできること
下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。
📦 インストール方法 (3ステップ)
- 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
- 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
- 3. 展開してできたフォルダを、ホームフォルダの
.claude/skills/に置く- · macOS / Linux:
~/.claude/skills/ - · Windows:
%USERPROFILE%\.claude\skills\
- · macOS / Linux:
Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。
詳しい使い方ガイドを見る →- 最終更新
- 2026-05-18
- 取得日時
- 2026-05-18
- 同梱ファイル
- 1
📖 Skill本文(日本語訳)
※ 原文(英語/中国語)を Gemini で日本語化したものです。Claude 自身は原文を読みます。誤訳がある場合は原文をご確認ください。
テスト戦略 Skill
目的
明確なカバレッジ目標とベストプラクティスを備えた最新のツール(Vitest、Playwright)を使用して、ユニットテスト、結合テスト、E2Eテストを網羅する包括的なテスト戦略を実装します。
この Skill を使用するタイミング
以下の場合に自動的に呼び出します。
- ユーザーが "test"、"testing"、"coverage"、"TDD"、"E2E" について言及した場合
- 新しいプロジェクトをセットアップする場合
- 新しい機能を追加する場合(テストが必要)
- テストの失敗をデバッグする場合
- テストカバレッジを改善する場合
テストピラミッド
/\
/E2E\ 少数、低速、高コスト
/------\
/ Integ \ いくつか、中程度の速度
/----------\
/ Unit Tests \ 多数、高速、低コスト
/--------------\
分布:
- 70% ユニットテスト - 高速、分離、低コスト
- 20% 結合テスト - 中程度の速度、インタラクションをテスト
- 10% E2Eテスト - 低速、高コスト、重要なユーザーフロー
テストの種類
1. ユニットテスト (Vitest)
内容: 個々の関数/コンポーネントを分離してテストします。
ツール: Vitest、React Testing Library
カバレッジ目標: 80%以上
セットアップ:
npm install -D vitest @vitest/ui @testing-library/react @testing-library/jest-dom
設定 (vitest.config.ts):
import { defineConfig } from 'vitest/config'
import react from '@vitejs/plugin-react'
export default defineConfig({
plugins: [react()],
test: {
globals: true,
environment: 'jsdom',
setupFiles: './tests/setup.ts',
coverage: {
provider: 'v8',
reporter: ['text', 'json', 'html'],
exclude: ['node_modules/', 'tests/'],
thresholds: {
lines: 80,
functions: 80,
branches: 75,
statements: 80
}
}
}
})
例 (Button.test.tsx):
import { render, screen, fireEvent } from '@testing-library/react'
import { describe, it, expect, vi } from 'vitest'
import { Button } from './Button'
describe('Button', () => {
it('renders with text', () => {
render(<Button>Click me</Button>)
expect(screen.getByText('Click me')).toBeInTheDocument()
})
it('calls onClick when clicked', () => {
const handleClick = vi.fn()
render(<Button onClick={handleClick}>Click</Button>)
fireEvent.click(screen.getByText('Click'))
expect(handleClick).toHaveBeenCalledOnce()
})
it('is disabled when disabled prop is true', () => {
render(<Button disabled>Disabled</Button>)
expect(screen.getByRole('button')).toBeDisabled()
})
})
コマンド:
npm run test # すべてのテストを実行
npm run test:watch # ウォッチモード
npm run test:ui # Visual UI
npm run test:coverage # カバレッジ付き
2. 結合テスト (Vitest)
内容: コンポーネントのインタラクション、API呼び出し、状態管理をテストします。
例 (UserProfile.test.tsx):
import { render, screen, waitFor } from '@testing-library/react'
import { describe, it, expect, vi } from 'vitest'
import { UserProfile } from './UserProfile'
// Mock API
vi.mock('./api', () => ({
fetchUser: vi.fn(() => Promise.resolve({
id: 1,
name: 'John Doe',
email: 'john@example.com'
}))
}))
describe('UserProfile Integration', () => {
it('fetches and displays user data', async () => {
render(<UserProfile userId="1" />)
expect(screen.getByText('Loading...')).toBeInTheDocument()
await waitFor(() => {
expect(screen.getByText('John Doe')).toBeInTheDocument()
expect(screen.getByText('john@example.com')).toBeInTheDocument()
})
})
})
3. E2Eテスト (Playwright)
内容: 実際のブラウザで完全なユーザーフローをテストします。
ツール: Playwright
カバレッジ目標: 重要なパスのみ
セットアップ:
npm install -D @playwright/test
npx playwright install
設定 (playwright.config.ts):
import { defineConfig, devices } from '@playwright/test'
export default defineConfig({
testDir: './e2e',
fullyParallel: true,
forbidOnly: !!process.env.CI,
retries: process.env.CI ? 2 : 0,
workers: process.env.CI ? 1 : undefined,
reporter: 'html',
use: {
baseURL: 'http://localhost:3000',
trace: 'on-first-retry',
},
projects: [
{
name: 'chromium',
use: { ...devices['Desktop Chrome'] },
},
{
name: 'mobile',
use: { ...devices['iPhone 13'] },
},
],
webServer: {
command: 'npm run dev',
url: 'http://localhost:3000',
reuseExistingServer: !process.env.CI,
},
})
例 (e2e/auth.spec.ts):
import { test, expect } from '@playwright/test'
test.describe('Authentication Flow', () => {
test('user can sign up and log in', async ({ page }) => {
// Sign up
await page.goto('/signup')
await page.fill('[name="email"]', 'test@example.com')
await page.fill('[name="password"]', 'SecurePass123!')
await page.click('button[type="submit"]')
// Should redirect to dashboard
await expect(page).toHaveURL(/\/dashboard/)
await expect(page.locator('h1')).toContainText('Welcome')
// Log out
await page.click('[aria-label="User menu"]')
await page.click('text=Logout')
// Should redirect to home
await expect(page).toHaveURL('/')
// Log back in
await page.goto('/login')
await page.fill('[name="email"]', 'test@example.com')
await page.fill('[name="password"]', 'SecurePass123!')
await page.click('button[type="submit"]')
await expect(page).toHaveURL(/\/dashboard/)
})
})
コマンド:
npx playwright test # すべてのE2Eを実行
npx playwright test --ui # インタラクティブモード
npx playwright test --headed # ブラウザを表示
npx playwright test --project=chromium # 特定のブラウザ
npx playwright show-report # 最後のレポートを表示
テストのベストプラクティス
AAAパターン
// Arrange
const user = { id: 1, name: 'John' }
const mockFetch = vi.fn()
// Act
const result = await fetchUser(mockFetch, 1)
// Assert
expect(result).toEqual(user)
expect(mockFetch).toHaveBeenCalledWith('/api/users/1') 📜 原文 SKILL.md(Claudeが読む英語/中国語)を展開
Testing Strategy Skill
Objective
Implement comprehensive testing strategy covering unit, integration, and E2E tests using modern tools (Vitest, Playwright) with clear coverage targets and best practices.
When to Use This Skill
Auto-invoke when:
- User mentions "test", "testing", "coverage", "TDD", "E2E"
- Setting up new project
- Adding new features (need tests)
- Debugging test failures
- Improving test coverage
Testing Pyramid
/\
/E2E\ Few, slow, expensive
/------\
/ Integ \ Some, moderate speed
/----------\
/ Unit Tests \ Many, fast, cheap
/--------------\
Distribution:
- 70% Unit Tests - Fast, isolated, cheap
- 20% Integration Tests - Moderate speed, test interactions
- 10% E2E Tests - Slow, expensive, critical user flows
Test Types
1. Unit Tests (Vitest)
What: Test individual functions/components in isolation
Tools: Vitest, React Testing Library
Coverage Target: 80%+
Setup:
npm install -D vitest @vitest/ui @testing-library/react @testing-library/jest-dom
Config (vitest.config.ts):
import { defineConfig } from 'vitest/config'
import react from '@vitejs/plugin-react'
export default defineConfig({
plugins: [react()],
test: {
globals: true,
environment: 'jsdom',
setupFiles: './tests/setup.ts',
coverage: {
provider: 'v8',
reporter: ['text', 'json', 'html'],
exclude: ['node_modules/', 'tests/'],
thresholds: {
lines: 80,
functions: 80,
branches: 75,
statements: 80
}
}
}
})
Example (Button.test.tsx):
import { render, screen, fireEvent } from '@testing-library/react'
import { describe, it, expect, vi } from 'vitest'
import { Button } from './Button'
describe('Button', () => {
it('renders with text', () => {
render(<Button>Click me</Button>)
expect(screen.getByText('Click me')).toBeInTheDocument()
})
it('calls onClick when clicked', () => {
const handleClick = vi.fn()
render(<Button onClick={handleClick}>Click</Button>)
fireEvent.click(screen.getByText('Click'))
expect(handleClick).toHaveBeenCalledOnce()
})
it('is disabled when disabled prop is true', () => {
render(<Button disabled>Disabled</Button>)
expect(screen.getByRole('button')).toBeDisabled()
})
})
Commands:
npm run test # Run all tests
npm run test:watch # Watch mode
npm run test:ui # Visual UI
npm run test:coverage # With coverage
2. Integration Tests (Vitest)
What: Test component interactions, API calls, state management
Example (UserProfile.test.tsx):
import { render, screen, waitFor } from '@testing-library/react'
import { describe, it, expect, vi } from 'vitest'
import { UserProfile } from './UserProfile'
// Mock API
vi.mock('./api', () => ({
fetchUser: vi.fn(() => Promise.resolve({
id: 1,
name: 'John Doe',
email: 'john@example.com'
}))
}))
describe('UserProfile Integration', () => {
it('fetches and displays user data', async () => {
render(<UserProfile userId="1" />)
expect(screen.getByText('Loading...')).toBeInTheDocument()
await waitFor(() => {
expect(screen.getByText('John Doe')).toBeInTheDocument()
expect(screen.getByText('john@example.com')).toBeInTheDocument()
})
})
})
3. E2E Tests (Playwright)
What: Test complete user flows in real browser
Tools: Playwright
Coverage Target: Critical paths only
Setup:
npm install -D @playwright/test
npx playwright install
Config (playwright.config.ts):
import { defineConfig, devices } from '@playwright/test'
export default defineConfig({
testDir: './e2e',
fullyParallel: true,
forbidOnly: !!process.env.CI,
retries: process.env.CI ? 2 : 0,
workers: process.env.CI ? 1 : undefined,
reporter: 'html',
use: {
baseURL: 'http://localhost:3000',
trace: 'on-first-retry',
},
projects: [
{
name: 'chromium',
use: { ...devices['Desktop Chrome'] },
},
{
name: 'mobile',
use: { ...devices['iPhone 13'] },
},
],
webServer: {
command: 'npm run dev',
url: 'http://localhost:3000',
reuseExistingServer: !process.env.CI,
},
})
Example (e2e/auth.spec.ts):
import { test, expect } from '@playwright/test'
test.describe('Authentication Flow', () => {
test('user can sign up and log in', async ({ page }) => {
// Sign up
await page.goto('/signup')
await page.fill('[name="email"]', 'test@example.com')
await page.fill('[name="password"]', 'SecurePass123!')
await page.click('button[type="submit"]')
// Should redirect to dashboard
await expect(page).toHaveURL(/\/dashboard/)
await expect(page.locator('h1')).toContainText('Welcome')
// Log out
await page.click('[aria-label="User menu"]')
await page.click('text=Logout')
// Should redirect to home
await expect(page).toHaveURL('/')
// Log back in
await page.goto('/login')
await page.fill('[name="email"]', 'test@example.com')
await page.fill('[name="password"]', 'SecurePass123!')
await page.click('button[type="submit"]')
await expect(page).toHaveURL(/\/dashboard/)
})
})
Commands:
npx playwright test # Run all E2E
npx playwright test --ui # Interactive mode
npx playwright test --headed # Show browser
npx playwright test --project=chromium # Specific browser
npx playwright show-report # View last report
Testing Best Practices
AAA Pattern
// Arrange
const user = { id: 1, name: 'John' }
const mockFetch = vi.fn()
// Act
const result = await fetchUser(mockFetch, 1)
// Assert
expect(result).toEqual(user)
expect(mockFetch).toHaveBeenCalledWith('/api/users/1')
Test Naming
// Good: descriptive, explains what and when
it('displays error message when API returns 404', () => {})
it('disables submit button when form is invalid', () => {})
// Bad: vague, unclear
it('works', () => {})
it('test 1', () => {})
One Assertion Per Test (Guideline)
// Prefer focused tests
it('renders user name', () => {
render(<User name="John" />)
expect(screen.getByText('John')).toBeInTheDocument()
})
it('renders user email', () => {
render(<User email="john@example.com" />)
expect(screen.getByText('john@example.com')).toBeInTheDocument()
})
// Over complex tests
it('renders user data', () => {
// Multiple unrelated assertions
})
Mock External Dependencies
// Mock API calls
vi.mock('./api', () => ({
fetchUser: vi.fn()
}))
// Mock environment
vi.stubEnv('API_URL', 'http://test-api.com')
// Mock timers
vi.useFakeTimers()
const now = new Date('2024-01-01')
vi.setSystemTime(now)
Coverage Strategy
What to Test
✅ Do Test:
- Business logic
- Edge cases and error handling
- User interactions
- API integration
- State management
- Validation logic
- Critical user flows (E2E)
❌ Don't Test:
- Third-party libraries
- Framework internals
- Constants
- Simple getters/setters
- Generated code
Coverage Targets
Minimum:
- Lines: 80%
- Functions: 80%
- Branches: 75%
- Statements: 80%
Ideal:
- Critical paths: 100%
- Business logic: 95%+
- UI components: 85%+
- Utilities: 90%+
Run Coverage
npm run test:coverage
# View in browser
open coverage/index.html
Testing Workflow
1. TDD Approach (Recommended)
1. Write failing test
2. Write minimal code to pass
3. Refactor
4. Repeat
2. Test-After (Pragmatic)
1. Implement feature
2. Write tests
3. Achieve 80%+ coverage
4. Refactor with confidence
3. Pre-Commit Testing
# Run before every commit
npm run test:quick # Fast unit tests
npm run lint
npm run typecheck
# Run before push
npm run test # All unit/integration
npm run test:coverage # Verify coverage
# Run before deploy
npm run test:e2e # Full E2E suite
Test Organization
Directory Structure
src/
├── components/
│ ├── Button/
│ │ ├── Button.tsx
│ │ ├── Button.test.tsx # Co-located
│ │ └── Button.stories.tsx # Storybook
│ └── ...
tests/
├── setup.ts # Test setup
├── utils/ # Test utilities
│ ├── renderWithProviders.tsx # Custom render
│ └── mockData.ts # Test fixtures
└── __mocks__/ # Global mocks
e2e/
├── auth.spec.ts
├── checkout.spec.ts
└── fixtures/ # E2E test data
Naming Conventions
- Unit/Integration:
*.test.tsor*.test.tsx - E2E:
*.spec.ts - Setup:
setup.ts,vitest.config.ts
Continuous Integration
GitHub Actions Example
name: Tests
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
node-version: 18
cache: 'npm'
- run: npm ci
- run: npm run lint
- run: npm run typecheck
- run: npm run test:coverage
- name: Upload coverage
uses: codecov/codecov-action@v3
with:
files: ./coverage/coverage-final.json
e2e:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
- run: npm ci
- run: npx playwright install --with-deps
- run: npm run build
- run: npx playwright test
- uses: actions/upload-artifact@v3
if: always()
with:
name: playwright-report
path: playwright-report/
Debugging Tests
Vitest
# Run single test file
npm run test -- Button.test.tsx
# Run tests matching pattern
npm run test -- --grep "Button renders"
# Debug in VS Code
# Add breakpoint, press F5
Playwright
# Debug mode
npx playwright test --debug
# Specific test
npx playwright test auth.spec.ts --debug
# Trace viewer
npx playwright show-trace trace.zip
Common Testing Patterns
Testing Async Code
it('fetches user data', async () => {
const { result } = renderHook(() => useUser(1))
await waitFor(() => {
expect(result.current.data).toEqual({ id: 1, name: 'John' })
})
})
Testing Error States
it('displays error when fetch fails', async () => {
vi.mocked(fetchUser).mockRejectedValue(new Error('Network error'))
render(<UserProfile userId="1" />)
await waitFor(() => {
expect(screen.getByText(/error/i)).toBeInTheDocument()
})
})
Testing Forms
it('submits form with valid data', async () => {
const handleSubmit = vi.fn()
render(<LoginForm onSubmit={handleSubmit} />)
await userEvent.type(screen.getByLabelText('Email'), 'test@example.com')
await userEvent.type(screen.getByLabelText('Password'), 'password123')
await userEvent.click(screen.getByRole('button', { name: /submit/i }))
expect(handleSubmit).toHaveBeenCalledWith({
email: 'test@example.com',
password: 'password123'
})
})
Integration with Other Skills
quality-gates- Run tests as quality checkgit-workflow- Tests in pre-commit hookscodebase-analysis- Identify untested code
Package.json Scripts
{
"scripts": {
"test": "vitest",
"test:watch": "vitest --watch",
"test:ui": "vitest --ui",
"test:coverage": "vitest --coverage",
"test:e2e": "playwright test",
"test:e2e:ui": "playwright test --ui",
"test:e2e:headed": "playwright test --headed",
"test:all": "npm run test:coverage && npm run test:e2e"
}
}
Version History
- 1.0.0 (2025-01-03): Initial testing strategy with Vitest and Playwright