<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.18.3">
</HEAD>
<BODY TEXT="#000000" BGCOLOR="#ffffff">
Thomas Diesler píše v Út 01. 11. 2011 v 18:29 +0000:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT>> will be solved by QEs using the integration-tests.sh script</TT><BR>
<BR>
<TT>The AS7 community project should not need to have a dedicated script to run test suites.</TT><BR>
</BLOCKQUOTE>
It doesn't need - but the script makes it easier to use.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<TT>What are these "irregularities" specifically?</TT><BR>
</BLOCKQUOTE>
That some test group runs by default and and needs to be disabled, while others do not run by default and need to be enabled.<BR>
With a script, one would simly specify which group of tests should be run, instead of passing a handful of options to mvn.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<TT>Perhaps you could present the problem and possible solution in a document that we can then discuss. </TT><BR>
</BLOCKQUOTE>
I use jira for that usually, but this issue was discussed in a mail thread within a closed group. I may fwd it here, or to you, if you like.<BR>
<BR>
Ondra<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<BR>
<TT>On 10/31/2011 11:04 PM, Ondřej Žižka wrote:</TT> <BR>
<BLOCKQUOTE TYPE=CITE>
<TT>The thing is, the groups are not mutually exclusive.</TT><BR>
<TT>Second, they are not (all) organized as maven modules.</TT><BR>
<BR>
<TT>But, afterall, it will be solved by QEs using the integration-tests.sh script which will hide these irregularities.</TT><BR>
<BR>
<TT>Ondra</TT> <BR>
<BR>
<BR>
<BR>
<TT>Thomas Diesler píše v Pá 28. 10. 2011 v 10:03 +0200:</TT> <BR>
<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:</TT><BR>
<BR>
<TT>-Dsuite=foo</TT><BR>
<TT>-Dsuite=bar</TT><BR>
<TT>-Dsuite=baz</TT><BR>
<TT>-Dsuite=...</TT><BR>
<BR>
<TT>in maven this would look like</TT><BR>
<BR>
<TT> <activation></TT><BR>
<TT> <property></TT><BR>
<TT> <name>suite</name></TT><BR>
<TT> <value>foo</value></TT><BR>
<TT> </property></TT><BR>
<TT> </activation></TT><BR>
<BR>
<TT>If 'foo' is the default (i.e. the smoke tests). You would also have profile that activates like this </TT><BR>
<BR>
<TT> <activation></TT><BR>
<TT> <property></TT><BR>
<TT> <name>!suite</name></TT><BR>
<TT> </property></TT><BR>
<TT> </activation></TT><BR>
<BR>
<TT>If the suites are organized my maven modules. You can AND them together with</TT><BR>
<BR>
<TT>mvn -pl testsuite-foo,testsuite-bar,testsuite-baz,...</TT><BR>
<BR>
<TT>It should always be possible to navigate to a particular module and run a subset of tests like this</TT><BR>
<BR>
<TT>mvn -Dtest=osgi/*/*TestCase test</TT><BR>
<BR>
<TT>cheers</TT><BR>
<TT>-thomas</TT><BR>
<BR>
<BR>
<BR>
<TT>On 10/27/2011 06:20 PM, Ondrej Zizka wrote: </TT><BR>
<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.</TT><BR>
<TT>Fixing.</TT><BR>
<BR>
<TT>Ondra</TT> <BR>
<BR>
<BR>
<BR>
<TT>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.</TT>
<TT>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.</TT>
<TT>On 27 Oct 2011, at 09:48, Thomas Diesler wrote:</TT>
<TT>> Currently, the smoke tests don't run as part of the build. Is this really what you want?</TT>
<TT>> </TT>
<TT>> <A 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></TT>
<TT>> </TT>
<TT>> -thomas</TT>
<TT>> </TT>
<TT>> On 10/27/2011 06:17 AM, Stuart Douglas wrote:</TT>
<TT>>> 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. </TT>
<TT>>> </TT>
<TT>>> Due to limitations in maven it is no longer possible to activate all tests using mvn install -DallTests, instead you should use either:</TT>
<TT>>> </TT>
<TT>>> ./build.sh install -DallTests - To do a full build with all tests</TT>
<TT>>> ./integration-tests.sh -DallTests - To just run all integration tests </TT>
<TT>>> </TT>
<TT>>> Running individual tests from an IDE or via mvn test -Dtest=MyTest should work as normal.</TT>
<TT>>> </TT>
<TT>>> 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.</TT>
<TT>>> </TT>
<TT>>> Stuart</TT>
<TT>>> </TT>
<TT>>> *<A HREF="https://docspace.corp.redhat.com/docs/DOC-74146">https://docspace.corp.redhat.com/docs/DOC-74146</A></TT>
<TT>>> *<A HREF="https://docspace.corp.redhat.com/docs/DOC-69049">https://docspace.corp.redhat.com/docs/DOC-69049</A> </TT>
<TT>>> *<A HREF="https://github.com/jbossas/jboss-as/pull/491">https://github.com/jbossas/jboss-as/pull/491</A></TT>
<TT>>> </TT>
<TT>>> </TT>
<TT>>> </TT>
<TT>>> _______________________________________________</TT>
<TT>>> jboss-as7-dev mailing list</TT>
<TT>>> </TT>
<TT>>> <A HREF="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</A></TT>
<TT>>> <A HREF="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</A></TT>
<TT>> </TT>
<TT>> -- </TT>
<TT>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx</TT>
<TT>> Thomas Diesler</TT>
<TT>> JBoss OSGi Lead</TT>
<TT>> JBoss, a division of Red Hat</TT>
<TT>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx </TT>
<TT>> </TT>
<TT>> _______________________________________________</TT>
<TT>> jboss-as7-dev mailing list</TT>
<TT>> <A HREF="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</A></TT>
<TT>> <A HREF="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</A></TT>
<TT>_______________________________________________</TT>
<TT>jboss-as7-dev mailing list</TT>
<TT><A HREF="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</A></TT>
<TT><A HREF="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</A></TT>
</PRE>
</BLOCKQUOTE>
<BR>
</BLOCKQUOTE>
<BR>
<PRE>
<TT>-- </TT>
<TT>xxxxxxxxxxxxxxxxxxxxxxxxxxxx</TT>
<TT>Thomas Diesler</TT>
<TT>JBoss OSGi Lead</TT>
<TT>JBoss, a division of Red Hat</TT>
<TT>xxxxxxxxxxxxxxxxxxxxxxxxxxxx </TT>
</PRE>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BR>
<PRE>
<TT>-- </TT>
<TT>xxxxxxxxxxxxxxxxxxxxxxxxxxxx</TT>
<TT>Thomas Diesler</TT>
<TT>JBoss OSGi Lead</TT>
<TT>JBoss, a division of Red Hat</TT>
<TT>xxxxxxxxxxxxxxxxxxxxxxxxxxxx </TT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>