elixir-tdd-enforcement

Test-driven development in Elixir starts by writing a failing ExUnit test that describes the desired behavior, running the test to confirm it fails (RED), then writing minimal production code to pass it (GREEN), and finally refactoring while keeping tests green. This cycle ensures tests drive your design.

Yes. TDD applies to any .ex file changes in lib/, including new functions, bug fixes, feature additions, behavior changes, and refactors. Every production code change requires a failing test first, guaranteeing test coverage from the start.

RED-GREEN-REFACTOR is a three-phase pattern: write a failing test (RED), implement minimal code to pass it (GREEN), then improve the code without breaking tests (REFACTOR). It prevents over-engineering, keeps code focused, and ensures tests always reflect production behavior.

Enforce a mandatory TDD workflow where any lib/ changes require a failing ExUnit test before implementation. This prevents untested production code by making the failing test a gating requirement before you write the actual feature or fix.

Yes. Refactoring within the TDD framework means keeping all existing tests green while you improve the code structure. Tests act as a safety net, ensuring behavior remains correct throughout the refactoring process.