Re: What I hate about *Unit frameworks.
Keith Ray <[email protected]>
| Newsgroups | gmane.comp.programming.test-driven-development |
|---|---|
| Message-ID | <[email protected]> |
> The fear of test cases interfering with each other was something that > was raised before we did the moves - but it turned out to be largely > baseless. I don't have the numbers to hand, but I do remember that we > found many more bugs that had been hidden by separate processes than > problems due to tests interfering with each other. > > Cheers, > > Adrian > One of the "Aha!" Epiphanies of a programmer I was working with, was the realization that a unit test only needs to test a "unit". He had been setting up real-life data, when a little "fake" data would verify the desired behavior. It also makes the code more robust, because side-effects that might not be seen in a system test, can be found by unit tests exercising all the edge-cases for each function or behavior being tested. > http://quietstars.com [email protected] twitter.com/adrianh > t. +44 (0)7752 419080 skype adrianjohnhoward pinboard.in/u:adrianh > [Non-text portions of this message have been removed] ------------------------------------ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/testdrivendevelopment/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/testdrivendevelopment/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/