On 08/06/2011 9:01 PM, Darren New wrote:
> Every work on unit testing I've read basically says you should run all
> the unit tests after each change, or certainly at least before each
> check-in.
>
> However, those same texts say that unit testing should only test
> individual units, and everything else should be mocked.
>
> Why would I want to run the unit tests for the XML parser after making
> changes to the color picker dialog box? Or, more generally, why would I
> want to run unit tests that are only executing code that hasn't changed
> since last time the unit tests passed?
>
> (Note I'm talking specifically of unit tests, not automated test suites
> in general.)
>

It doesn't make sense to me. If you're going to run all unit tests after 
one change then you might as well call it a system test.
It sounds as if someone is trying to cover their back. IMO It is not 
feasible to run all UT after a change. You would never get the 
implementation finished.

But then I've never read anything on the theory although I've 15 full 
implementations. As long as you do unit, system, integration and 
possibly regression testing before UAT then you will be OK. IMO.

-- 
Regards
     Stephen

Post a reply to this message