<!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>
Update on the update :)<BR>
<BR>
The concept of having sources in different dir than the module running it may provoke some controversy.<BR>
Here's my brief explanation:<BR>
<BR>
<FONT SIZE="2"><FONT COLOR="#cc0000">(05:54:13) </FONT></FONT><FONT COLOR="#cc0000">stuartdouglas: </FONT><FONT COLOR="#000000">Why is it good for running from the IDE?</FONT><BR>
<FONT SIZE="2"><FONT COLOR="#cc0000">(05:54:35) </FONT></FONT><FONT COLOR="#cc0000">stuartdouglas: </FONT><FONT COLOR="#000000">I would have though that having the source in the wrong module would stop that from working althogether</FONT><BR>
<FONT SIZE="2"><FONT COLOR="#cc0000">(05:59:07) </FONT></FONT><FONT COLOR="#cc0000">stuartdouglas: </FONT><FONT COLOR="#000000">I really dislike having the sources in the wrong module, it makes things considerably more complicated and non-standard, and I don't really see the advantage of it </FONT><BR>
<FONT SIZE="2"><FONT COLOR="#204a87">(06:00:22) </FONT></FONT><FONT COLOR="#204a87">OndrejZizka1: </FONT><FONT COLOR="#909090">Which ide?</FONT><BR>
<FONT SIZE="2"><FONT COLOR="#204a87">(06:00:34) </FONT></FONT><FONT COLOR="#204a87">OndrejZizka1: </FONT><FONT COLOR="#909090">The idea is to run the integration module with different profiles</FONT><BR>
<FONT SIZE="2"><FONT COLOR="#204a87">(06:00:45) </FONT></FONT><FONT COLOR="#204a87">OndrejZizka1: </FONT><FONT COLOR="#909090">That way it's transparent</FONT><BR>
<FONT SIZE="2"><FONT COLOR="#204a87">(06:02:17) </FONT></FONT><FONT COLOR="#204a87">OndrejZizka1: </FONT><FONT COLOR="#909090">In other words, running mvn install would still run the smoke tests and results would be in surefire-reports,</FONT><BR>
<FONT SIZE="2"><FONT COLOR="#204a87">(06:02:22) </FONT></FONT><FONT COLOR="#204a87">OndrejZizka1: </FONT><FONT COLOR="#909090">+ HTML report,</FONT><BR>
<FONT SIZE="2"><FONT COLOR="#204a87">(06:02:33) </FONT></FONT><FONT COLOR="#204a87">OndrejZizka1: </FONT><FONT COLOR="#909090">and mvn install -DallTests would run all,</FONT><BR>
<FONT SIZE="2"><FONT COLOR="#204a87">(06:02:58) </FONT></FONT><FONT COLOR="#204a87">OndrejZizka1: </FONT><FONT COLOR="#909090">and also going to testsuite/integration and running mvn install -DallTests would work</FONT><BR>
<FONT SIZE="2"><FONT COLOR="#204a87">(06:03:32) </FONT></FONT><FONT COLOR="#204a87">OndrejZizka1: </FONT><FONT COLOR="#909090">The devs wouldn't touch submodules</FONT><BR>
<BR>
Maven/IDE experts please correct me if my assumptions are wrong. I use NetBeans which work fine with this concept.<BR>
<FONT COLOR="#909090">But after all, the code can be separated, I am not strictly against nor for.</FONT><BR>
<BR>
Ondra<BR>
<BR>
<BR>
<BR>
<BR>
Ondřej Žižka píše v Pá 11. 11. 2011 v 05:50 +0100:<BR>
<BLOCKQUOTE TYPE=CITE>
Hi everyone,<BR>
<BR>
as was discussed on this list, the current testsuite harness had some problems fulfilling even basic requirements for various use cases, including but not limited to:<BR>
* Using from IDE through pure maven<BR>
* -DallTests vs. individial modules vs. distinctive groups vs. even overlaying groups<BR>
* Configuring AS using kind of hierarchical templates<BR>
* Imposing certain test groups order<BR>
* Invoking only some steps of the testsuite<BR>
* Running same tests with different AS configuration<BR>
etc etc.<BR>
<BR>
I've been working on an updated concept, which is currently at <A HREF="https://github.com/OndraZizka/jboss-as/commits/TS-modules-tmp">https://github.com/OndraZizka/jboss-as/commits/TS-modules-tmp</A> .<BR>
I would like you to review it, run it, and send me some comments.<BR>
<BR>
cd testsuite/integration<BR>
mvn clean install -f pom2.xml -DallTests -fae<BR>
mvn clean install -f pom2.xml -Dts.iiop<BR>
<BR>
(There are 2 pom.xml's so I can compare two harnesses easily.)<BR>
The scripts are not updated yet so they do not work.<BR>
CLI and OSGi tests fail. To be sorted out.<BR>
<BR>
<BR>
The big news are:<BR>
<BR>
* Execution split to modules<BR>
* Code and resources remained in the same location<BR>
* Added few system properties which provide paths to important directories - see <A HREF="https://docs.jboss.org/author/display/AS71/AS+7+Testsuite+Test+Developer+Guide">https://docs.jboss.org/author/display/AS71/AS+7+Testsuite+Test+Developer+Guide</A><BR>
* Work directory is now in target/workdir<BR>
<BR>
These cahnges exposed some issues in test code which need to be fixed - hardcoded relative paths.<BR>
Since there were no system properties to use, there was no other way, but from now on please use those properties, and fix your existing tests.<BR>
(This would happen anyway because some tests clutter workdir (which happens to be module's root dir) with various temp files.)<BR>
<BR>
<BR>
Thanks,<BR>
Ondra<BR>
<BR>
<BR>
<BR>
<PRE>
_______________________________________________
jboss-as7-dev mailing list
<A HREF="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</A>
<A HREF="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</A>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>