2024 Public Training Schedule
November 18 – 21, 2024 – Agile Analysis and Design Patterns
Half-Day Sessions
December 9 – 12, 2024 – Agile Analysis and Design Patterns
Half-Day Sessions
Follow me on Twitter:
Blog Post Categories
- Announcements {19}
- Articles {2}
- Bits and Pieces {74}
- Blogosphere {1}
- Bonuses {2}
- Build in Small Batches {27}
- Collaborate {38}
- Create CLEAN Code {34}
- Implement the Design Last {11}
- Integrate Continuously {30}
- Off-Topic but Interesting {3}
- Rants {82}
- Refactor Legacy Code {24}
- Say What, Why, and for Whom Before How {22}
- Seven Strategies {38}
- Specify Behaviors with Tests {17}
- Write the Test First {27}
Archives
Privacy Policy
(c) 2024 To Be Agile
- October 28, 2009
- Write the Test First
Rarely is failure a good thing in life but in test driven development a failing test can be a very good thing. Many TDD developers dread the “red bar” but it is really worth celebrating and here’s why.
Developers are often under the mistaken impression that TDD is about getting to the “green bar”. This is actually untrue; TDD is about turning the red bar green! We must first get to the red bar to prove that our test can fail. A test that cannot fail is a test that is worse than worthless; it is a lie that gives us a false sense of security! Seeing the red bar first verifies that our test can fail and so we know it will serve us when it needs to.
Previous Post: « Bits and Pieces
Next Post: When Are Tests Most Valuable? »