Re^2: Fine line between integration testing and unit testing

Why? (he asks curiously :-)

Because it seems like killing two birds with one stone (which probably means: I want the benefit of automated testing without testing every single code path)

Thanks for the reply.

--------------
badaiaqrandista

Comment on Re^2: Fine line between integration testing and unit testing

Replies are listed 'Best First'.
Re^3: Fine line between integration testing and unit testing by adrianh (Chancellor) on May 11, 2006 at 08:46 UTC
Because it seems like killing two birds with one stone (which probably means: I want the benefit of automated testing without testing every single code path) The problem you'll get is that it suddenly gets a whole lot more complicated to diagnose problems if something breaks in that middle layer that's not being explicitly tested. You also end up running more and longer tests since you can't test components in isolation.	[reply]

Replies are listed 'Best First'.

Re^3: Fine line between integration testing and unit testing
by adrianh (Chancellor) on May 11, 2006 at 08:46 UTC

Because it seems like killing two birds with one stone (which probably means: I want the benefit of automated testing without testing every single code path)

The problem you'll get is that it suddenly gets a whole lot more complicated to diagnose problems if something breaks in that middle layer that's not being explicitly tested. You also end up running more and longer tests since you can't test components in isolation.

[reply]