tdd-workflow

Topics in the source

• TDD Workflow
• 1. The TDD Cycle
• 2. The Three Laws of TDD
• 3. RED Phase Principles
• What to Write
• RED Phase Rules
• 4. GREEN Phase Principles
• Minimum Code

Write tests first, code second. -- -- 1. Write production code only to make a failing test pass 2. Write only enough test to demonstrate failure 3. Write only enough code to make the test pass -- | Focus | Example | |-------|---------| | Behavior | "should add two numbers" | | Edge cases | "should handle empty input" | | Error states | "should throw for invalid data" | Test must fail first Test name describes expected behavior One assertion per test (ideally) -- | Principle | Meaning | |-----------|---------| | YAGNI | You Aren't Gonna Need It | | Simplest thing | Write the minimum to pass | | No optimization | Just make it work | Don't write unneeded code Don't optimize yet Pass the test, nothing more -- | Area | Action | |------|--------| | Duplication | Extract common code | | Naming | Make intent clear | | Structure | Improve organization | | Complexity | Simplify logic | All tests must stay green Small incremental changes Commit after each refactor -- Every test follows: | Step | Purpose | |------|---------| | Arrange | Set up test data | | Act | Execute code under test | | Assert | Verify expected outcome | -- | Scenario | TDD Value | |----------|-----------| | New feature |

This is an excerpt. Refer to the complete source and its current requirements.