tdd-bug-fix

Test-driven bug fixing means writing a failing test first that reproduces the bug, verifying it fails (red), then implementing the minimal production fix and verifying the test passes (green). This ensures every bug fix has regression protection and follows Kent Beck's Red-Green-Refactor workflow.

Writing a test first captures the bug's exact behavior, confirms you've reproduced it, and creates a checkpoint to verify your fix works. Tests written before the fix prevent the same bug from reoccurring and document expected behavior for future maintainers.

Place tests in your project's standard test directory—commonly spec/, test/, or __tests__/—following your framework and language conventions. This ensures tests are discovered by your test runner and aligned with your project's testing standards.

Yes, TDD bug-fix practice works across common languages and test frameworks including RSpec, Jest, pytest, and others. The Red-Green-Refactor workflow applies regardless of framework; the core discipline is writing a failing test, then minimal production code.

Regular debugging finds and fixes issues ad-hoc; TDD bug fixes enforce a disciplined workflow: failing test first, then fix, then verification. This approach produces regression tests automatically and prevents production changes without accompanying test coverage.

Your bug fix is complete when the previously failing test now passes (green) and your implementation uses only the minimal code changes needed to make that test pass. Then refactor if needed, ensuring all tests remain green throughout.