[infinispan-dev] Infinispan smoke tests?

[Adrian Cole]

good idea.  CI can always run your smoke tests and help ensure they
are at least run somewhere ;)

The only thing that's a bugger is that the surefire plugin doesn't
honor groups very well.  We'd have to name these tests *SmokeTest (or
place in a different dir) and setup a special maven profile "smoke"
which includes them in the integration-test phase.  As you might
guess, we'd have to modify the default integration-test to exclude
them.

yay maven! ;)

-Adrian

On Fri, Sep 4, 2009 at 7:49 AM, Galder
Zamarreno<galder.zamarreno at redhat.com> wrote:
> Hi,
>
> Due to the complexity of tests that have been added to the Infinispan
> test suite, the time it takes to run the testsuite has almost doubled.
> These tests (i.e. distribution rehashing, non-blocking state transfer)
> need to be run, that's for sure.
>
> However, I was thinking whether we could create a brand new group of
> tests called "smoke". The aim here is for the tests in that group to run
> lightning fast and cover 90% of the testsuite.
>
> I think this would help find most of the regressions that are sometimes
> introduced for not running the testsuite locally.
>
> Once hudson issues have been solved, we'll be in a better situation but
> I still think having this 'smoke' group could help avoid regressions.
> Obviously, the danger here is people always running this profile and
> then discovering loads of test fails when the entire testsuite is run
> but we have this issue now too.
>
> Thoughts?
> --
> Galder Zamarreño
> Sr. Software Engineer
> Infinispan, JBoss Cache
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>