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

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

One thing we talked about internally is that lthough not much thought has gone into what makes up the smoke tests, at least they are good for picking up problems in parsing and management layer which is very useful as a pre-pull request requirement. We had a look around and found: http://maven.apache.org/guides/introduction/introduction-to-profiles.html which mentions: "As of Maven 3.0, profiles in the POM can also be activated based on properties from active profiles from the setttings.xml.". Here is the rest of the discussion: [27/10/2011 14:29:01] Stuart Douglas: but that requires a specific settings.xml [27/10/2011 14:29:06] Kabir Khan: Oh [27/10/2011 14:29:11] Stuart Douglas: although [27/10/2011 14:29:31] Stuart Douglas: we coud just require all the QA people to have a specific settings.xml [27/10/2011 14:31:43] Kabir Khan: Yeah, I've not really looked at the current setup so I don't know if it would work or not but if it does I'm all for it [27/10/2011 14:36:42] Jason T. Greene: we bundle maven with as though [27/10/2011 14:36:58] Jason T. Greene: and there is a settings.xml in there [27/10/2011 14:37:41] Jason T. Greene: so we could put it all in there [27/10/2011 14:38:07] Stuart Douglas: but really we need to settings.xml [27/10/2011 14:38:16] Stuart Douglas: the the default developer one [27/10/2011 14:38:21] Stuart Douglas: and the QE one [27/10/2011 14:38:25] Jason T. Greene: sure [27/10/2011 14:38:30] Jason T. Greene: thats reaosnable imo [27/10/2011 14:38:32] Kabir Khan: qe-build.sh :-) [27/10/2011 14:38:45] Stuart Douglas: and hopefully that will work better On 27 Oct 2011, at 17:20, 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 >

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

> will be solved by QEs using the integration-tests.sh script The AS7 community project should not need to have a dedicated script to run test suites.

What are these "irregularities" specifically?

Perhaps you could present the problem and possible solution in a document that we can then discuss.

On 10/31/2011 11:04 PM, Ondřej Žižka wrote: > 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 -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler JBoss OSGi Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

Smoke tests are running by default now which is nice. However, a './build.sh clean install -DallTests=true' no longer runs all the tests, while they did last week. This is starting to get very confusing, all I want to do is to process some pull requests and run the tests. If this really needs to keep changing all the time, a this-is-how-we-run-the-tests-today.txt file in the root folder would help :-) On 27 Oct 2011, at 17:20, 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 > _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

It would be nice if we could agree which parameters should actually work and what they mean - the one that caught me out recently was when -DskipTests=true was broken. Regards, Darran Lofthouse. On 11/03/2011 11:34 AM, Kabir Khan wrote: > Smoke tests are running by default now which is nice. However, a './build.sh clean install -DallTests=true' no longer runs all the tests, while they did last week. This is starting to get very confusing, all I want to do is to process some pull requests and run the tests. > > If this really needs to keep changing all the time, a this-is-how-we-run-the-tests-today.txt file in the root folder would help :-) > > On 27 Oct 2011, at 17:20, 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 > > _______________________________________________ > 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

Smoke tests are running by default now which is nice. However, a './build.sh clean install -DallTests=true' no longer runs all the tests, while they did last week. This is starting to get very confusing, all I want to do is to process some pull requests and run the tests. If this really needs to keep changing all the time, a this-is-how-we-run-the-tests-today.txt file in the root folder would help :-)

On 27 Oct 2011, at 17:20, 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 > _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev