Stephen wrote:
> My understanding of unit testing is that they are just used to test one 
> aspect of the software, independently. 

Sure. But if you have one "aspect" that takes a dozen steps to set up, and 
those steps might fail, do you check each of those previous worked (which 
means you're testing a bunch of stuff, possibly obscuring what you really 
want to test), or do you assume they worked because you already tested them 
(making the tests not independent)?

-- 
Darren New, San Diego CA, USA (PST)
   Human nature dictates that toothpaste tubes spend
   much longer being almost empty than almost full.

Post a reply to this message