Well I could test it some more but...
Posted: Tue Aug 01, 2006 10:36 am
Mods: This isn't about testing as such more about the emotional response to programming so I think Theory and Design is more appropriate also i'm more interested in the comment from more advanced developers
Do any of you experience this:
Now obviously this is a really stupid thing to do and yet I still do it. Frequently it gets me into trouble as well, especially now I've started writing OO code. It is much easier to write a class and test it thoroughly before proceeding, this one of the nice things about OO because you can then be certain about what works and what doesn't because everything is compartmentalized. Of course if you don't bother to test stuff it could be anything and this means that most of the time finding the error is harder than actually fixing it. Sometimes I have to think about which directory of files the problem might be in, and then which file before I can isolate the problem to a single function.
The moral of this story is Don't do an Ole! test thoroughly before writing anymore. But then again, is that sometimes counter-productive?
Do any of you experience this:
- You have just spent ages writing something.
- You're pretty sure you've got it right and you've tested it once; none of those E_ messages come up and it appears to work.
- So you are happy. xD
- You are so happy in fact you don't want anything to spoil that happiness. Something like.....testing it some more perhaps.
Now obviously this is a really stupid thing to do and yet I still do it. Frequently it gets me into trouble as well, especially now I've started writing OO code. It is much easier to write a class and test it thoroughly before proceeding, this one of the nice things about OO because you can then be certain about what works and what doesn't because everything is compartmentalized. Of course if you don't bother to test stuff it could be anything and this means that most of the time finding the error is harder than actually fixing it. Sometimes I have to think about which directory of files the problem might be in, and then which file before I can isolate the problem to a single function.
The moral of this story is Don't do an Ole! test thoroughly before writing anymore. But then again, is that sometimes counter-productive?