|
|
|
|
|
by Klathmon
3275 days ago
|
|
That's exactly how I've always done it, and it works beautifully for me. Put "test stubs" out there that define what I'm testing in "human" terms, leave the stub either skipped or failing. I've also found that if I wait a day or 2 after writing the implementation to write the tests, they catch much more. If you write the code to match the tests, or you write the tests right after the code the chance that both the test and the code are wrong is much higher in my experience than if you wait a bit and come back to write the tests with fresh eyes. |
|