The use of multiple surefire executions per module is inherently
problematic AFAICS. Maven addresses the need to fail at the end by the
conveniently called -fae switch - it works across multiple modules.
I'd say a better approach would be to split the testsuite in sets of one
server configuration each. You'd have a single surefire
configuration/execution per module. Test sources can be reused between
modules via standard dependencies. Multiple modules can be executed
together using -pl. The full testrun can fail at the end with -fae
Ondřej, could you please check whether the multiple executions approach
is even valid. E2 must run even if you have failures in E1. Especially
if E2 contains the majority of tests.
cheers
-thomas
On 11/25/2011 10:00 PM, Ondřej Žižka wrote:
Regarding this - I have added new -DallInteg for the purpose of
running all integration without benchmark, stress etc. (Again, need
to re-test that after rebasing.)
See
https://docs.jboss.org/author/display/AS71/AS+7+Integration+Testsuite+Use...
.
Ondra
> BTW, -DallTests is no option because that includes benchmarks, stress, clustering,
which I would want only Jenkins to run.
>
> cheers
> -thomas
> --
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thomas Diesler
> JBoss OSGi Lead
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx