On Monday 17 November 2003 17:08, Ulrich Mayring wrote: > Niclas Hedhman wrote: > > On Saturday 15 November 2003 05:41, Ulrich Mayring wrote: > >>And I hate unit-testing, I'd rather prove my code correct ;-) > > > > You never miss an opportunity to point this out, LOL... > > > > Curious, how can you "prove" anything without running it? > > Very hard, but all I said was I'd rather do that than do unit-testing ;-) > > The thing is that of the bugs I have in my software, 99% would not have > been caught by unit tests, because they are runtime bugs (integration, > error management, external resources etc.). The remaining 1% are trivial > bugs such as typos, which take me about 1 minute to fix.
Ok... I think we have had this argument before, but the "best thing" of UT (to me) is not so much the capturing of bugs but that I quicker find good use-cases, and know that this design is not well-structured. The "second best thing" actually drives back to your 99%... If a user finds a problem, you need to spend time to set up a test rig. If all UTs are already in place is faster to get going on the particular case to be found... > I do think that for developing frameworks with many well-defined > interfaces there may be some value in unit testing. > > Although there is probably a good reason why it's not done > systematically at Avalon ;-) TDD requires a lot of discipline. I don't have it. As soon as TDD becomes tricky (like the GUI I'm working on), TDD is dropped quickly because you want to get on with it (I think this is the main reason why not everyone do TDD). Cheers, Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
