Quote:

---

Doug: I've heard a lot of good things about test driven a lot recently. Sounds like a type of "prototype iteration" to me. The key is to define the right test then, right? Good test will lead to good code; bad test will lead to bad code, yes/no?

---

I'm not sure what you mean by "bad test". If you write a test that expects a bad value (e.g. A test that makes sure the player's health doesn't *reach* 0 even when you want to test that it doesn't go *under* zero) you can catch it later on with more tests (e.g. when check to see that the player can die, you'll notice that you used '>' when you wanted '>=').

But you don't normally write bad tests because most of them are so small (3-4 lines).