6:04 p.m.
The thing is, the groups are not mutually exclusive.
Second, they are not (all) organized as maven modules.
But, afterall, it will be solved by QEs using the integration-tests.sh
script which will hide these irregularities.
Ondra
Thomas Diesler píše v Pá 28. 10. 2011 v 10:03 +0200:
Is it really that hard? Lets assume you have a set of mutually
exclusive test suites. They could be organized like this:
-Dsuite=foo
-Dsuite=bar
-Dsuite=baz
-Dsuite=...
in maven this would look like
<activation>
<property>
<name>suite</name>
<value>foo</value>
</property>
</activation>
If 'foo' is the default (i.e. the smoke tests). You would also have
profile that activates like this
<activation>
<property>
<name>!suite</name>
</property>
</activation>
If the suites are organized my maven modules. You can AND them
together with
mvn -pl testsuite-foo,testsuite-bar,testsuite-baz,...
It should always be possible to navigate to a particular module and
run a subset of tests like this
mvn -Dtest=osgi/*/*TestCase test
cheers
-thomas
On 10/27/2011 06:20 PM, Ondrej Zizka wrote:
> Ok, seems like QA will have to carry the burden of disabling smoke
> tests whenever they want to run anything else - because Maven's
> profile activation logic really sucks.
> Fixing.
>
> Ondra
>
>
>
> On Thu, 2011-10-27 at 11:36 +0100, Kabir Khan wrote:
>
> > The smoke tests must be run as part of a standard build. Please fix.
> >
> > If QE have other requirements, which are not possible to combine with the above
requirement maybe they should look into using alternate poms or the antrun plugin or
something.
> > On 27 Oct 2011, at 09:48, Thomas Diesler wrote:
> >
> > > Currently, the smoke tests don't run as part of the build. Is this
really what you want?
> > >
> > >
https://hudson.qa.jboss.com/hudson/view/JBossOSGi/job/jboss-as7-master/389/
> > >
> > > -thomas
> > >
> > > On 10/27/2011 06:17 AM, Stuart Douglas wrote:
> > >> I just just merged some changes to the test suite that QE requires for
EAP (see below for a link to their requirements). As a result the manner in which the
tests are run has changed slightly.
> > >>
> > >> Due to limitations in maven it is no longer possible to activate all
tests using mvn install -DallTests, instead you should use either:
> > >>
> > >> ./build.sh install -DallTests - To do a full build with all tests
> > >> ./integration-tests.sh -DallTests - To just run all integration tests
> > >>
> > >> Running individual tests from an IDE or via mvn test -Dtest=MyTest
should work as normal.
> > >>
> > >> Ondej Zizka (in CC) has been the person working on these changes, so
if you have any questions or comments he is the person to talk to.
> > >>
> > >> Stuart
> > >>
> > >> *https://docspace.corp.redhat.com/docs/DOC-74146
> > >> *https://docspace.corp.redhat.com/docs/DOC-69049
> > >> *https://github.com/jbossas/jboss-as/pull/491
> > >>
> > >>
> > >>
> > >> _______________________________________________
> > >> 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
> > >
> > > _______________________________________________
> > > jboss-as7-dev mailing list
> > > jboss-as7-dev(a)lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> >
> >
> > _______________________________________________
> > 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