テストカバレッジの計測、ギャップ分析、改善計画の策定を行うスキル。 リスクベースで優先順位を決め、実行可能な改善ステップに落とし込む。 Anchors: • Working Effectively with Legacy Code / 適用: リスク評価 / 目的: 重点領域の特定 • xUnit Test Patterns / 適用: テスト設計 / 目的: 有効なテスト追加 • Test-Driven Development: By Example / 適用: テスト追加 / 目的: 品質改善 Trigger: Use when analyzing test coverage, prioritizing coverage gaps, or planning coverage improvements. test coverage, coverage report, coverage gap, risk-based testing, improvement plan
Write comprehensive tests with emphasis on ALL error paths, edge cases, and regression coverage for code changes
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
Given-When-Then 形式の受け入れ基準を整理し、テスト可能な完了条件の定義を支援する。 要件の明確化、シナリオ設計、検証手順を一貫して整理する。 Anchors: • Software Requirements (Karl Wiegers) / 適用: 要件分析・仕様化 / 目的: テスト可能な要件定義 • BDD in Action (John Ferguson Smart) / 適用: Given-When-Then / 目的: 振る舞い駆動開発 • The Art of Software Testing (Glenford Myers) / 適用: テスト設計 / 目的: 検証可能性の確保 Trigger: 受け入れ基準の作成、ユーザーストーリーの仕様化、テスト可能な要件定義を行う場合に使用。 acceptance criteria, user story, GWT, Given-When-Then, testable requirements, definition of done
Generate test cases for code. Use when writing unit tests, integration tests, or verifying acceptance criteria.
Write integration tests with Jest for API routes and database operations. Use when testing backend logic, API endpoints, or data layer.
Screenshot capture, organization, and comparison for QA testing. Use when taking screenshots during test execution to ensure proper naming, organization, and traceability back to test cases.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Comprehensive frontend testing strategy encompassing component tests, visual regression, accessibility, and E2E testing for modern web applications using Vitest, React Testing Library, Playwright, and Storybook. Anchors: • Test-Driven Development: By Example (Kent Beck) / Apply: Red-Green-Refactor cycle / Purpose: Guide test-first development workflow • Testing Library Guiding Principles / Apply: Query priorities and user-centric testing / Purpose: Ensure tests resemble user behavior • WCAG 2.1 AA Standards / Apply: Automated accessibility testing / Purpose: Ensure inclusive UI components Trigger: Use when implementing or improving frontend tests, setting up test infrastructure, debugging failing tests, improving test coverage, or establishing testing best practices for React/Next.js applications. vitest, react testing library, playwright, storybook, component test, e2e test, visual regression, accessibility testing, test coverage, mock service worker
Go repository testing with SQLC integration following hexagonal architecture. Use when writing integration tests for repository layer, testing database operations, and validating domain model persistence. Focuses on testcontainers, table-driven tests, and comprehensive error coverage.
Create or update test files for React hooks. Use when user asks to "create hook tests", "test useMyHook", "generate tests for hook", "update hook tests", or mentions needing tests for a React hook. Generates vitest test files with renderHook, Fake context providers, and proper test structure.
Generates test mocks, stubs, and fixtures for testing (Jest, Vitest, pytest, etc.). Use when user asks to "create mock", "generate stub", "mock function", "test fixtures", or "mock API response".
Red-Green-Refactorサイクルを中心にTDDを実行するための専門スキル。 失敗テストの設計、最小実装、リファクタを反復し、品質と速度を両立する。 Anchors: • Test-Driven Development: By Example / 適用: RGRサイクル / 目的: 反復の規律 • Refactoring (Martin Fowler) / 適用: 改善手順 / 目的: 振る舞い維持 • xUnit Test Patterns / 適用: テスト設計 / 目的: 表現の一貫性 Trigger: Use when focusing on the red-green-refactor cycle, coaching TDD execution, or reviewing cycle quality. red-green-refactor, TDD cycle, failing test, minimal implementation, refactoring
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
テストダブルの選択・設計・検証を一貫して整理するスキル。 依存関係の分離と検証戦略を統一し、テストの意図と可読性を高める。 Anchors: • Test-Driven Development: By Example / 適用: テストダブル選択 / 目的: テスト意図の明確化 • xUnit Test Patterns / 適用: テストパターン / 目的: ダブル設計の一貫性 Trigger: Use when choosing, designing, or validating test doubles such as mocks, stubs, fakes, or spies. test doubles, mock, stub, fake, spy
Generates complete test suite infrastructure (test scripts, functional tests, benchmark tests, output directories, CMake integration) for a new SDL3 HammerEngine system or manager following project conventions. Use when adding a new manager or system that needs testing infrastructure.
QA best practices and test design patterns. Use when designing test cases to ensure comprehensive coverage with equivalence partitioning, boundary analysis, and accessibility testing.
Automated UI testing for web applications using Playwright with comprehensive test coverage and reporting
Guide for writing Gherkin acceptance criteria using Given-When-Then syntax for testable requirements. Covers scenario structure, background blocks, scenario outlines with examples tables, common patterns for authentication/CRUD/validation/error handling, and best practices for clear testable specifications. Essential for writing user stories and plan acceptance criteria
Validates implementations against specifications by checking requirements coverage, acceptance criteria, and documentation updates
Write behavior-focused Agile user stories with BDD-style acceptance criteria. Use when defining features, clarifying requirements, or creating development tickets. Produces narrative-form stories with Given-When-Then scenarios.
Verify Definition of Done and acceptance criteria for Sprint increments. Use when completing sprints, running verification commands, or preparing for acceptance.
