Unit Testing

Write minimal, strategic tests focused on core user flows and critical paths rather than comprehensive coverage. When creating or modifying test files for unit tests, integration tests, or end-to-end tests. When working on test files (*.test.ts, *.spec.ts, __tests__/*). When writing tests for critical user workflows and primary functionality. When testing behavior rather than implementation details. When mocking external dependencies or ensuring fast test execution. When deciding which parts of the codebase require testing coverage.

Architecture patterns for rRNA-Phylo project including FastAPI backend design, service organization, async task processing with Celery, Pydantic schemas, testing with pytest, Biopython integration, and API design conventions. Covers project structure, dependency injection, error handling, and configuration management.

Testing, performance optimization, security, and Play Store deployment. Use when shipping production apps.

Configure Vitest for unit and integration testing. Use when setting up a test framework, when no test runner is detected, or when the user asks to configure testing.

Use Functional Core, Imperative Shell pattern to isolate deterministic business logic from side-effect orchestration for improved testability.

Manage iOS delivery builds to QC testing with GitLab pipeline creation and issue management. Supports develop, delivery, bugfix, and redelivery modes. Use when "create delivery", "delivery build", "build for qc", "send to testing", or "deliver build".

Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Documentation in llms.txt format, (3) GitHub repository analysis, (4) Documentation without direct llms.txt support, (5) Multiple documentation sources in parallel

Use when user says "verify story", "check acceptance criteria", "validate implementation", "is story ready", or asks to verify that an implemented story meets its acceptance criteria - parses acceptance criteria from story description, verifies each with test/code evidence, generates pass/fail report, and updates story status based on results.

SwiftプロジェクトのビルドとテストをXcodeコマンドラインで実行（iOS/macOS対応）。Use when: ビルド、テスト、xcodebuild、swift test を依頼された時。

Generates test cases, creates mocks, identifies edge cases, analyzes coverage gaps, and supports property-based, mutation, and contract testing. Use when writing tests, improving coverage, detecting flaky tests, or implementing advanced testing strategies.

Write Vitest unit tests and browser mode component tests for TypeScript projects. Use when asked to write tests, create test files, add test coverage, fix failing tests, test React components with browser mode, or work with Vitest testing patterns. Handles both unit testing with Given-When-Then pattern and React component testing with vitest-browser-react.

Tests JavaScript and TypeScript applications with Vitest including unit tests, mocking, coverage, and React component testing. Use when writing tests, setting up test infrastructure, mocking dependencies, or measuring code coverage.

Analyze existing PHPUnit test failure logs without running tests. Use when:- User says "fix the test failures" (after manually running tests)- User says "what tests are failing?"- User points to specific log file- Tests were run outside Claude's contextDelegates to fixer agent (sonnet) to find logs, parse failures, and implement fixes.Does NOT execute tests - use phpunit-runner for that.

Use when writing Python tests, setting up test suites, or implementing testing best practices. Covers pytest, fixtures, mocking, and test-driven development.

Deploys applications to cloud Kubernetes (AKS/GKE/DOKS) with CI/CD pipelines.Use when deploying to production, setting up GitHub Actions, troubleshooting deployments.Covers build-time vs runtime vars, architecture matching, and battle-tested debugging.

Use when adding features or fixing bugs. Follow RED/GREEN/REFACTOR cycle. Write failing test first, implement minimal code to pass, then refactor.

Run unit tests using CTest. Use when user asks to run tests, test the code, check test results, or mentions test failures.

Framework for writing and reviewing tests. Use when creating new tests, reviewing test quality, or debugging flaky tests.

Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

Build amplifier-foundation modules using "bricks and studs" architecture. Covers tool, hook, provider, context, and orchestrator modules with testing, publishing, and best practices.