|Problems? Is your data what you think it is?|
Re^5: Does anybody write tests first?by BrowserUk (Pope)
|on Feb 23, 2008 at 22:17 UTC||Need Help??|
All of that to get a line number that perl gives you for free?
And, you have had to re-run the failing test file using prove (which seems to be a different version to that I have?) instead of the make test.
And how am I meant to get my editor to pick the line number out of all the rest of that redundant crap?
16 lines of ouput for 1 that is useful. A simple die unless 1 == 2; achieves the same thing without all the redundancy. And if it's located in the code being tested, the line number will lead directly the the source file that needs fixing instead of a test file that I then have to manually relate to the appropriate source file.
And what happens when the test calls a function, that calls a function in another module, that fails. Do you get traceback?
It's just layer upon layer of complexity, taking you further and further away from the real code, for the sake of producing a set of meaningless statistics that nobody cares about.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.