testing-best-practices
Comprehensive guide to writing effective unit, integration, and end-to-end tests with modern testing frameworks
Comprehensive guide to writing effective unit, integration, and end-to-end tests with modern testing frameworks
Execute frontend implementation with TDD. Read all constraint files before coding, write failing test first, verify after each step. Use this skill when: - User asks to "implement this", "implement the plan", "start implementation", "execute plan" - Have an implementation plan ready and need to execute it - Executing steps from /frontend.plan output - User says "start coding", "write the code", "begin implementation" - User asks to "use TDD", "write test first", "test-driven" for frontend code - User asks to "write tests", "add tests", "create tests" - Fixing UI bugs (write failing test that reproduces bug first) TDD Iron Law: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST TDD Cycle: RED (write failing test) → Verify fails → GREEN (minimal code) → Verify passes → REFACTOR Prerequisites: - MUST have task file in docs/reference/frontend/tasks/ (use /frontend.tasks first if not exists) - MUST read design-system.md, constraints.md, and design spec before writing any code. Flow: Check Task File → Read Constrai
Unit testing, integration testing, and test-driven development principles. Use when writing tests, reviewing test code, improving test coverage, or setting up testing strategy. Triggers on "write tests", "review tests", "testing best practices", or "TDD".
Review existing tests for completeness, quality issues, and common mistakes
Running and validating Probitas scenarios. Use when executing tests, running scenarios, or debugging test failures.
Use when encountering any bug, test failure, or unexpected behavior. Always find root cause before attempting fixes. Evidence before assertions.
Enables Claude to create and manage documents in Craft via Playwright MCP
End-to-end testing with Playwright including page objects, fixtures, visual regression, and CI integration. Use for E2E test implementation or test architecture.
Playwright MCPを使用してWebアプリケーションを探索的にテストし、バグや問題を発見します。手動テストの代替や品質保証の補助に使用します。
Load testing, chaos engineering, and performance validation. Prove your system works under pressure with k6, trace correlation, and progressive load profiles.
Testing patterns for GoGoJap project. Use when writing tests, creating mocks, or following TDD workflow.
AI-driven test generation with mutation testing and property-based testing. Research shows property-based tests find 50x more bugs than unit tests. Use when: - Need comprehensive test coverage for new code - Coverage gaps identified in existing code - Implementing TDD and need test scaffolding - Want to validate test quality with mutation testing - Edge cases need systematic discovery - Refactoring and need regression safety net Do NOT use for: - Trivial one-liner functions - Generated code with known patterns - Simple CRUD operations (use templates instead)
CUI MockWebServer standards for HTTP client testing with JUnit 5 integration
Essential testing patterns for any project. Use when: writing tests, setting up testing, or fixing test issues. Triggers: "test", "testing", "unit test", "write tests".
Generate pytest test templates for LiquidationHeatmap modules following TDD patterns. Automatically creates RED phase tests with fixtures, coverage markers, and integration test stubs.
Translates iOS workflow markdown files into Playwright E2E tests for CI using WebKit with mobile viewport. Use this when the user says "convert ios workflows to playwright", "translate ios workflows to CI", or wants to promote refined iOS/mobile workflows to automated CI tests.
API testing patterns for MiGestion - Jest, Supertest, mocking. Trigger: When writing or running API unit tests.
Expert test writing including unit, integration, e2e tests, mocking, and coverage strategies