<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
        <table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
                <tbody>
                        <tr>
                                <td>
                                        <table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
                                                <tbody>
                                                        <tr>
                                                                <td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
                                                                        <h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
                                                                        <!-- To have a header image/logo replace the name below with your img tag -->
                                                                        <!-- Email clients will render the images when the message is read so any image -->
                                                                        <!-- must be made available on a public server, so that all recipients can load the image. -->
                                                                        <a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
                                                                </td>
                                                        </tr>
                                                        <tr>
                                                                <td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
JBossWS - Running the test suites
</h3>
<span style="margin-bottom: 10px;">
modified by <a href="http://community.jboss.org/people/asoldano">Alessio Soldano</a> in <i>JBoss Web Services Development</i> - <a href="http://community.jboss.org/docs/DOC-13523">View the full document</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p><div class="toc" style="border: 1px dashed black; padding: 10px;"><ul><ul><ul><li>
<a class="jive-link-anchor-small" href="#Working_with_the_integration_layers">Working with the integration layers</a>
</li>
<ul><li>
<a class="jive-link-anchor-small" href="#Ant_build">Ant build</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Maven__Ant_build">Maven + Ant build</a>
</li>
</ul><li>
<a class="jive-link-anchor-small" href="#Working_with_JBossWSNative">Working with JBossWS-Native</a>
</li>
<ul><li>
<a class="jive-link-anchor-small" href="#Ant_build_680091">Ant build</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Maven__Ant_build_342531">Maven + Ant build</a>
</li>
</ul><li>
<a class="jive-link-anchor-small" href="#Working_with_JBossWSCXF">Working with JBossWS-CXF</a>
</li>
<ul><li>
<a class="jive-link-anchor-small" href="#Ant_build_488716">Ant build</a>
</li>
<li>
<a class="jive-link-anchor-small" href="#Maven__Ant_build_109493">Maven + Ant build</a>
</li>
</ul><li>
<a class="jive-link-anchor-small" href="#Working_with_the_Hudson_QA_environment">Working with the Hudson QA environment</a>
</li>
<ul><li>
<a class="jive-link-anchor-small" href="#Maven__Ant_build_778894">Maven + Ant build</a>
</li>
</ul></ul></ul></ul></div></p><p>Typically you would build, deploy, test one of the web service stacks against one of the supported target containers. Here we explain first the manual procedure. Further down you find instruction on how to do this using our automated Hudson QA environment.</p><p>Please not two different builds are available, Ant and Maven+Ant, as the binary distribution does not use Maven.</p><h3 id="Working_with_the_integration_layers">Working with the integration layers</h3><p>To run the general JAX-WS samples against our native WS stack on JBoss-6.0 you would run the sequence below. This is also the required sequence before any SVN commit. If one of the tests fails, please complain loudly.</p><h4 id="Ant_build">Ant build</h4><div class="note"><p><em><strong>Note</strong></em></p><p style="padding-left: 30px;"><em>Make sure to <strong>modify ant.properties</strong> accordingly before running the tasks below. Running the tests against another target container simply means changing the ant.properties calling "<tt>ant deploy-jboss510</tt>" for instance. Also please note that the provided Ant targets may change from release to release because of different supported AS containers; calling "ant -projecthelp" is often a good idea to understand which targets are available.</em></p></div><pre class="jive-pre"><code class="jive-code"> 
cd stack/native/trunk
ant deploy-jboss600
ant tests-main
ant tests-samples
</code></pre><p>To run the collection of provider sample tests, you would run</p><pre class="jive-pre"><code class="jive-code">ant -Dtest=jaxws/samples/provider test
</code></pre><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>To run a single specific test, you would run</p><pre class="jive-pre"><code class="jive-code jive-java">ant -Dtest=org.jboss.test.ws.jaxws.samples.provider.ProviderPayloadTestCase one-test
</code></pre><p>This can be done in debug mode as well</p><pre class="jive-pre"><code class="jive-code"> ant -Ddebug=true -Dtest=org.jboss.test.ws.jaxws.samples.provider.ProviderPayloadTestCase one-test
</code></pre><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h4 id="Maven__Ant_build">Maven + Ant build</h4><div class="note"><p><em><strong>Note</strong></em></p><p style="padding-left: 30px;"><em>Make sure to <strong>copy/modify profiles.xml.example/profiles.xml</strong> accordingly before running the tasks below. Running the tests against another target container both means changing the deploy ant command ("ant deploy-jboss510" for instance) and the specified maven profile when running the tests. This simply means changing the specified profile to "<tt>jboss510</tt>" for instance. Also please note that the provided target profiles may change from release to release because of different supported AS containers.</em></p></div><pre class="jive-pre"><code class="jive-code">cd stack/native/trunk
ant deploy-jboss600
mvn -Ptestsuite,jboss600 test
</code></pre><p>To run the collection of provider sample tests, you would run</p><pre class="jive-pre"><code class="jive-code">mvn -Ptestsuite,jboss600 -Dtest=jaxws/samples/provider test
</code></pre><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>To run a single specific test, you would run</p><pre class="jive-pre"><code class="jive-code">mvn -Ptestsuite,jboss600 -Dtest=jaxws/samples/provider/ProviderPayloadTestCase test
</code></pre><p>This can be done in debug mode as well</p><pre class="jive-pre"><code class="jive-code">mvn -Ptestsuite,jboss600 -Dtest=jaxws/samples/provider/ProviderPayloadTestCase -Dmaven.surefire.debug=true test
</code></pre><p>Finally, depending on the Maven version you're using, you might need to set the jbossXYZ.home property:</p><pre class="jive-pre"><code class="jive-code">mvn -Ptestsuite,jboss600 -Djboss600.home=/home/user/jboss/build/output/jboss-6.0.0.Final test
</code></pre><h3 id="Working_with_JBossWSNative">Working with JBossWS-Native</h3><p>The jbossws native test-suite is a super set of the general JAX-WS test-suite. It tests our native stack, JAX-RPC, the tools layer, etc. This shows how to run the full core test-suite against JBoss-6.0</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h4 id="Ant_build_680091">Ant build</h4><pre class="jive-pre"><code class="jive-code">cd stack/native/trunk
./build.sh deploy-jboss600
./build.sh tests-main
./build.sh tests
</code></pre><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h4 id="Maven__Ant_build_342531">Maven + Ant build</h4><p>When running the testsuite, the Maven build always performs both common and stack specific tests, so nothing different from what's explained above in "Working with the integration layers" is required.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h3 id="Working_with_JBossWSCXF">Working with JBossWS-CXF</h3><p>The jbossws cxf test-suite is a super set of the general JAX-WS test-suite. It tests the jbossws-cxf integration, JAX-RPC, the tools layer, etc. This shows how to run the full core test-suite against JBoss-6.0</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h4 id="Ant_build_488716">Ant build</h4><pre ___default_attr="plain" jivemacro="code">cd stack/cxf/trunk<br/>./build.sh deploy-jboss600<br/>./build.sh tests-main<br/>./build.sh tests<br/></pre><h4 id="Maven__Ant_build_109493">Maven + Ant build</h4><p>When running the testsuite, the Maven build always performs both common and stack specific tests, so nothing different from what's explained above in "Working with the integration layers" is required.</p><p>Starting from 3.4.0 just keep in mind that SpringFramework dependencies are not triggered by default anymore. You can add Spring to the testsuite client classpath as well as enable additional tests relying on Spring using the custom "spring" maven profile:</p><pre class="jive-pre"><code class="jive-code">mvn -Ptestsuite,jboss600,spring test
</code></pre><h3></h3><h3 id="Working_with_the_Hudson_QA_environment">Working with the Hudson QA environment</h3><p>The Hudson QA environment helps you to test any supported stack against any supported target container.</p><h4 id="Maven__Ant_build_778894">Maven + Ant build</h4><p>The Hudson setup is still based on Ant. You just need to checkout the jbossws-framework and move to the "hudson" directory.</p><pre class="jive-pre"><code class="jive-code">cd jbossws/framework/trunk/hudson
ant hudson-setup
ant hudson-start
</code></pre><p><br/> When you hit <a class="jive-link-external-small" href="http://localhost:8180/hudson">http://localhost:8180/hudson</a> you should be able to</p><ul><li> log-in </li><li> build a target container </li><li> run a test-suite against the target container </li></ul><p>Publicly, Hudson is available at <a class="jive-link-external-small" href="http://jbossws.jboss.org:8180/hudson/">http://jbossws.jboss.org:8180/hudson/</a> (or <a class="jive-link-external-small" href="http://jbossws.jboss.org:8280/hudson/">http://jbossws.jboss.org:8280/hudson/</a> during QA release phase)</p></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Comment by <a href="http://community.jboss.org/docs/DOC-13523">going to Community</a></p>
        <p style="margin: 0;">Create a new document in JBoss Web Services Development at <a href="http://community.jboss.org/choose-container!input.jspa?contentType=102&containerType=14&container=2047">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>