Re: By Bullshitters, For Bullshitters
some arsehole thinks that "testing starts at day one"
and even the TRIVIAL things, like 1+1=2, MUST have a test function to verify it STILL works!!!
if I developed test functions for EVERYTHING I wrote, the test suite would probably be LARGER than the actual code. AND, there would be no value added. Because, when testing is needed, I do that separately, then put the function in place ONE TIME, shelve the "test the algorithm" console mode program [in case I ever need to look at it, which I never seem to] and document how the function works in case someone ELSE has to work with it. No need to re-re-re-test it EVERY! STINKING! TIME! because it WORKS.
And, if all functions (that aren't trivial) are tested in this manner, are well documented, and guaranteed to do what's on the tin, then you're fine.
[and also assuming that the project isn't shotgunned across way too many files with way too many trivial functions calling even more trivial functions ad infinitum so you can't even see the code flow any more without having 67 files open at the same time, JUST so you can do "unit tests" on EVERYTHING]
icon, because, facepalm
Biting the hand that feeds IT
