generating-tdd-tests
TDD with RGRC cycle and Baby Steps methodology. Use when implementing features with test-driven development, following RGRC cycle, or when user mentions TDD, テスト駆動, Red-Green-Refactor, Baby Steps.
TDD with RGRC cycle and Baby Steps methodology. Use when implementing features with test-driven development, following RGRC cycle, or when user mentions TDD, テスト駆動, Red-Green-Refactor, Baby Steps.
Pixel-perfect visual testing with auto-fix loop. Implement → Render → Snapshot → Compare → Fix until pass.
Write tests with TDD. Supports Jest, Cypress, Detox, PHPUnit, PyTest, Go testing.
Use Vercel's agent-browser CLI for automated browser testing and UI verification. Use when: (1) browser-based quality gates are required, (2) verifying UI behavior in the browser, (3) gathering screenshots or DOM evidence during Ralph execution. This replaces Playwriter MCP usage.
Fast bug fixes with TDD. Lightweight: understand → test → fix → verify.
Testing workflow tools following Modified-Code Protocol for intelligent test selection.
Validate load balancer behavior, failover, and traffic distribution. Use when performing specialized testing. Trigger with phrases like "test load balancer", "validate failover", or "check traffic distribution".
Write behavior-focused tests following Testing Trophy model with real dependencies, avoiding common anti-patterns like testing mocks and polluting production code
Write the test first, watch it fail, write minimal code to pass
TDD for process documentation - test with subagents before writing, iterate until bulletproof
Apply testing patterns like AAA (Arrange-Act-Assert), mocking, fixtures, and parameterization for maintainable test suites
Generate Compose UI tests for Android and Kotlin Multiplatform projects. Use when: (1) Writing tests for @Composable functions, (2) Creating screenshot/snapshot tests, (3) Testing state changes and user interactions in Compose UI, (4) Adding test coverage to screens. Triggers: "compose test", "ui test", "write tests for", "test this composable", "screenshot test", "paparazzi", "roborazzi", "compose testing".
MANDATORY when writing tests. Test behavior, not implementation. Functional tests are primary. Unit tests ONLY for state mutations. Includes fixing flaky tests with condition-based waiting.
Integration test workflow using spies (testFixtures) in TMDB-Android. Use when writing integration tests with remote/local spies to follow established setup, naming, and state/paging assertions.
Execute integration tests validating component interactions and system integration. Use when performing specialized testing. Trigger with phrases like "run integration tests", "test integration", or "validate component interactions".
Add platform adapter, templates, tests with 100% coverage, and README documentation
Use when implementing UI components, design systems, or responsive layouts - verifies visual correctness through screenshot comparison and DevTools verification; prevents shipping broken UI
Use when changing code structure with intended behavior changes (performance optimizations, rewrites, module splits, sync-to-async, data model shifts, cleanup that may alter outputs or timing) - enforces explicit behavior boundaries, baseline tests, and verification to prevent regressions.
Configure unit testing with Bun's built-in test runner. Fast, Jest-compatible syntax, co-located test files, and mocking support.
End-to-end browser testing with Playwright. Test user interactions, form validation, navigation, and visual feedback with full browser automation.
Replace arbitrary timeouts with condition polling for reliable async tests