Re: Long running test suite

A common approach is to split your tests by type (unit, integration, UI),
or at least by speed (fast, slow). Then, always run the fast tests before
check-in, but let the build/CI server run the slow tests (all the tests).
This way, you're able to check in frequently but you still have the CI
server there to catch anything your unit tests (the fast ones) miss.

If you're not sure whether your tests are unit or integration tests, I
wrote about the differences a while ago here:
http://ardalis.com/unit-test-or-integration-test-and-why-you-should-care

Steve


On Sun, May 22, 2016 at 11:25 PM, Joselito D Moreno [email protected]
[testdrivendevelopment] <[email protected]> wrote:

>
>
> Hello,
>
> To those who have experienced test suites that run long, say ~25 minutes,
> what are some techniques you have used to mitigate it?  We still would like
> to be able to check in often and run the test suites prior to checking our
> code in to our repository but these long running tests makes us stretch
> what we mean with "often".
>
> Joen
>
> 
>



-- 
Steve Smith
http://Ardalis.com/
http://twitter.com/ardalis