Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
TDD stands for Test-Driven Development, or Test-Driven Design. It is the practice of writing a unit test before writing code to satisfy it, in what is known as the Red-Green-Refactor cycle.
197
votes
Accepted
Does TDD make defensive programming redundant?
TDD forces code to pass tests and forces all code to have some tests around it. … TDD will develop the tests. Implementing parameter validation will make them pass. …
12
votes
TDD Red-Green-Refactor and if/how to test methods that become private
You don't do TDD based on what you expect the class will do internally.
Your test cases should be based on what the class/functionality/program has to do to the external world. … The flow of TDD is:
red (what is the class/object/function/etc doing to the external world)
green (write the minimal code to make this external world function work)
refactor (what is the better code …