tdd▌

Test-driven development for Laravel applications using PHPUnit and Pest with 80%+ coverage (unit + feature).

Writes failing tests first, establishing a strict implementation contract for test-driven development. \n \n Completes the RED phase of TDD by authoring behavior-focused tests that fail for the right reason, then hands off to implementation agents with objective pass criteria \n Delegates test authoring to a tdd_test_writer subagent when available, ensuring tests remain unmodified during implementation \n Detects existing test frameworks and conventions (pytest, jest, vitest, go test, cargo test

def product_list(request): products = Product.objects.all() return JsonResponse({'products': list(products.values())})

Test-driven development workflow enforcing 80%+ coverage across unit, integration, and E2E tests. \n \n Write tests first, then implement code to make them pass; covers unit tests (functions, components), integration tests (APIs, databases), and E2E tests (Playwright for critical user flows) \n Includes comprehensive testing patterns with Jest/Vitest for components, API route testing, and Playwright for browser automation workflows \n Provides mocking strategies for external services (Supabase,

Comprehensive TDD guide for Django with pytest, factory_boy, and DRF API testing. \n \n Covers the red-green-refactor cycle with pytest configuration, test settings, and conftest fixtures for models, views, and API endpoints \n Factory Boy patterns for creating test data, including sequences, relationships, and post-generation hooks \n Model, view, serializer, and API ViewSet testing strategies with real code examples for CRUD operations and filtering \n Mocking and patching techniques for exter

Test-driven development framework for Spring Boot with JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo enforcement. \n \n Covers unit tests (Mockito), web layer tests (MockMvc), integration tests (SpringBootTest), and persistence tests (DataJpaTest) with concrete examples \n Integrates Testcontainers for production-mirroring Postgres/Redis databases and JaCoCo for enforcing 80%+ code coverage \n Emphasizes Arrange-Act-Assert patterns, AssertJ assertions, and test data builders for maintain

Write comprehensive failing tests following TDD red phase principles.

Execute a comprehensive Test-Driven Development (TDD) workflow with strict red-green-refactor discipline:

Test-driven development with vertical slices, behavior-focused tests, and incremental red-green-refactor cycles. \n \n Emphasizes integration-style tests that verify behavior through public APIs, not implementation details; tests should survive refactors unchanged \n Requires vertical slicing (one test → one implementation → repeat) instead of horizontal slicing (all tests first, then all code), preventing brittle, behavior-insensitive test suites \n Includes planning phase to confirm interface