<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>> will be solved by QEs using the integration-tests.sh script<br>
<br>
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. <br>
<br>
On 10/31/2011 11:04 PM, Ondřej Žižka wrote:</tt>
<blockquote cite="mid:1320102292.6321.8.camel@ondra-redhat"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<tt> The thing is, the groups are not mutually exclusive.<br>
Second, they are not (all) organized as maven modules.<br>
</tt>
<meta name="GENERATOR" content="GtkHTML/3.18.3">
<tt><br>
But, afterall, it will be solved by QEs using the
integration-tests.sh script which will hide these
irregularities.<br>
<br>
Ondra</tt>
<tt><br>
<br>
<br>
<br>
Thomas Diesler píše v Pá 28. 10. 2011 v 10:03 +0200:</tt>
<tt><br>
</tt>
<blockquote type="CITE"> <tt>Is it really that hard? Lets assume
you have a set of mutually exclusive test suites. They could
be organized like this:<br>
<br>
</tt> <tt>-Dsuite=foo<br>
</tt> <tt>-Dsuite=bar<br>
</tt> <tt>-Dsuite=baz<br>
</tt> <tt>-Dsuite=...<br>
<br>
</tt> <tt>in maven this would look like<br>
<br>
</tt> <tt> <activation><br>
</tt> <tt> <property><br>
</tt> <tt> <name>suite</name><br>
</tt> <tt> <value>foo</value><br>
</tt> <tt> </property><br>
</tt> <tt> </activation><br>
<br>
</tt> <tt>If 'foo' is the default (i.e. the smoke tests). You
would also have profile that activates like this <br>
<br>
</tt> <tt> <activation><br>
</tt> <tt> <property><br>
</tt> <tt> <name>!suite</name><br>
</tt> <tt> </property><br>
</tt> <tt> </activation><br>
<br>
</tt> <tt>If the suites are organized my maven modules. You can
AND them together with<br>
<br>
</tt> <tt>mvn -pl testsuite-foo,testsuite-bar,testsuite-baz,...<br>
<br>
</tt> <tt>It should always be possible to navigate to a
particular module and run a subset of tests like this<br>
<br>
</tt> <tt>mvn -Dtest=osgi/*/*TestCase test<br>
<br>
</tt> <tt>cheers<br>
</tt> <tt>-thomas<br>
<br>
<br>
<br>
On 10/27/2011 06:20 PM, Ondrej Zizka wrote: </tt> <tt><br>
</tt>
<blockquote type="CITE"><tt> 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.<br>
Fixing.<br>
<br>
Ondra</tt> <tt><br>
<br>
<br>
<br>
On Thu, 2011-10-27 at 11:36 +0100, Kabir Khan wrote: </tt>
<blockquote type="CITE">
<pre><tt>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?
>
> <a moz-do-not-send="true" href="https://hudson.qa.jboss.com/hudson/view/JBossOSGi/job/jboss-as7-master/389/">https://hudson.qa.jboss.com/hudson/view/JBossOSGi/job/jboss-as7-master/389/</a>
>
> -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
>>
>> *<a moz-do-not-send="true" href="https://docspace.corp.redhat.com/docs/DOC-74146">https://docspace.corp.redhat.com/docs/DOC-74146</a>
>> *<a moz-do-not-send="true" href="https://docspace.corp.redhat.com/docs/DOC-69049">https://docspace.corp.redhat.com/docs/DOC-69049</a>
>> *<a moz-do-not-send="true" href="https://github.com/jbossas/jboss-as/pull/491">https://github.com/jbossas/jboss-as/pull/491</a>
>>
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>>
>> <a moz-do-not-send="true" href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a>
>> <a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a>
>
> --
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thomas Diesler
> JBoss OSGi Lead
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> _______________________________________________
> jboss-as7-dev mailing list
> <a moz-do-not-send="true" href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a>
> <a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a>
_______________________________________________
jboss-as7-dev mailing list
<a moz-do-not-send="true" href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a>
<a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a>
</tt></pre>
</blockquote>
<tt><br>
</tt> </blockquote>
<tt><br>
</tt>
<pre><tt>--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
</tt></pre>
</blockquote>
</blockquote>
<tt><br>
</tt>
<pre class="moz-signature" cols="72"><tt>--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
</tt></pre>
</body>
</html>