tdd-workflow

A structured TDD workflow drives red-green-refactor cycles across backend pytest and frontend vitest, ensuring one test per acceptance criterion with deterministic checks before minimal code implementation.

Handling AssertionError and ImportError during test-driven development involves stepwise red-green cycles where you write failing tests, implement minimal code to pass, and refactor iteratively within the Planner→Tester→Builder pipeline.

Yes, vitest and pytest can run together in a single TDD pipeline. The workflow guides writing tests for each acceptance criterion across frontend and backend, enforcing deterministic runs and systematic refactoring.

Writing deterministic tests for each acceptance criterion requires creating one isolated test per criterion, using model_bakery for backend fixtures and vitest for frontend, then running them to fail before writing code.

TDD refactoring works with task decomposition in an Audit Platform by breaking down tasks through the Planner→Tester→Builder→Reviewer→Archivist pipeline, guiding stepwise cycles and regression testing across the stack.

A test-driven development cycle stalls during refactor when deterministic checks are not enforced. The workflow provides explicit guidance on stepwise cycles, ensuring tests pass before and after code changes to maintain momentum.