|Problems? Is your data what you think it is?|
Re^2: A danger of test driven development.by Perl Mouse (Chaplain)
|on Oct 03, 2005 at 12:01 UTC||Need Help??|
Whenever two pieces of code disagree, verify that the simpler one is correct (cause it's simpler to verify), then check the more complex one.
I did, and the test looked ok.
You shouldn't have to change code to pass tests
Really? You never change code? All the code you write is correct, always? You never make typos, swap arguments, popped instead of shifted? Lucky you, you don't need any tests!
It sounds like you wrote too much untested code at once.
No, I didn't. I did write enough chunks of code between test runs to actually have compilable, no non-sense code though.