You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by vm...@apache.org on 2005/01/29 09:09:40 UTC
cvs commit: jakarta-cactus/documentation/docs/xdocs/integration index.xml
vmassol 2005/01/29 00:09:40
Modified: documentation/docs/xdocs/integration index.xml
Log:
Improved integration page description of the different solutions. Hopefully it is more clear and fixes CACTUS-162.
Revision Changes Path
1.7 +51 -26 jakarta-cactus/documentation/docs/xdocs/integration/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-cactus/documentation/docs/xdocs/integration/index.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- index.xml 18 Mar 2004 22:13:15 -0000 1.6
+++ index.xml 29 Jan 2005 08:09:40 -0000 1.7
@@ -32,45 +32,70 @@
<p>
The Cactus tests are started using a JUnit Test Runner. There are
- several configurations for executing these test runners:
+ several integration clients you can use for executing these test runners:
</p>
<ul>
<li>
- <link href="site:integration_ant">From Ant</link>, by using the
- <code><cactifywar></code> and <code><cactus></code>
- custom Ant tasks.
+ <link href="site:integration_manual">Manually</link>. This means
+ that you need to deploy your code and tests into your container and
+ start this container by yourself. Then you can execute the tests
+ by running a standard JUnit test Runner. For example, you can start
+ the tests:
+ <ul>
+ <li>
+ From the java command line, calling the <code>main()</code>
+ method of a JUnit Test Runner. For example, running the JUnit
+ Swing Test Runner:
+ <code>junit.swingui.TestRunner.main [test case class]</code>
+ </li>
+ <li>
+ <link href="site:howto_ide">From an IDE</link> or any tool
+ providing a JUnit integration plugin.
+ </li>
+ <li>
+ <link href="site:integration_browser">From a browser</link>, by
+ using the Cactus Servlet Test Runner, which is a special JUnit
+ Test Runner. Please also check the
+ <link href="site:howto_tomcat">Tomcat quick start tutorial</link>
+ which is a step by step tutorial describing how to deploy Cactus
+ tests in Tomcat and how to execute them through a browser.
+ </li>
+ <li>
+ From Ant by simply using the <code><junit></code> Ant task
+ found in the Ant distribution.
+ </li>
+ </ul>
</li>
<li>
- <jump anchor="from_command_line">From the java command line</jump>,
- calling the <code>main()</code> method of a JUnit Test Runner.
+ Using the Cactus <link href="site:integration_ant">Ant
+ integration</link>. Cactus provides several custom Ant task to
+ automate the deployment of Cactus tests
+ (<code><cactifywar></code>) and the
+ start/stop/configuration of your container
+ (<code><cactus></code>). Note that you can also use the
+ custom <code><runservertests></code> Ant task which allows you
+ to use your existing container configuration should you wish to.
</li>
<li>
- <link href="site:howto_ide">From an IDE</link> or any tool
- providing a JUnit integration plugin.
+ Using the Cactus <link href="ext:integration_maven">Maven
+ plugin</link>. As with the Ant tasks this plugin offers a fully
+ automated solution to deploy and execute Cactus tests.
</li>
<li>
- <link href="site:integration_browser">From a browser</link>, by
- using the Cactus Servlet Test Runner, which is a special JUnit
- Test Runner.
+ Using the <link href="site:integration_jetty">Jetty
+ integration</link>. Cactus provides a
+ <code>JettyTestSetup</code> class that you can directly
+ use in your Cactus TestCase's <code>suite()</code> method. This
+ <code>TestSetup</code> class will automatically configure and start
+ Jetty for you before the tests are executed and it will stop it once
+ the tests are finished. The nice thing is that starting Jetty takes
+ only a few hundreds of milliseconds making this solution the fastest
+ one to execute your Cactus tests. Obviously it is only interesting if
+ you wish to test using Jetty.
</li>
</ul>
</section>
- <anchor id="from_command_line"/>
- <section title="Running Cactus tests from the command line">
-
- <p>
- You need to set up your classpath in the same way as when you run
- Cactus tests from Ant. However, you start the test with the following
- command line (this is an example using the Swing UI TestRunner found
- in the junit jar):
- </p>
- <p>
- <code>junit.swingui.TestRunner.main [test case class]</code>
- </p>
-
- </section>
-
</body>
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org