vmassol 01/08/20 11:52:46
Modified: cactus/docs/framework/xdocs index.xml
Log:
positionned Cactus amongst the several unit testing frameworks
Revision Changes Path
1.24 +43 -19 jakarta-commons/cactus/docs/framework/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/cactus/docs/framework/xdocs/index.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- index.xml 2001/08/19 17:54:10 1.23
+++ index.xml 2001/08/20 18:52:46 1.24
@@ -42,25 +42,49 @@
<figure src="images/archiani.gif" alt="How it works ..."/></link>
</p>
</s1>
- <s1 title="What Cactus is not !">
- <p>
- Cactus is not :
- </p>
- <ul>
- <li>
- A functional testing framework offering black box testing. Instead
- Cactus provides white box testing. For a functional testing
- framework, see
- <link href="http://sourceforge.net/projects/httpunit";>HttpUnit
- </link>.
- </li>
- <li>
- A mock objects implementation of server-side APIs. As mentionned
- above, Cactus has chosen from the beginning to focus on
- in-container testing. For a mock objects implementation, see the
- <link href="http://www.mockobjects.com";>Mock Objects</link> project.
- </li>
- </ul>
+
+ <s1 title="Different kind of unit tests">
+
+ <p>
+ There are several kinds of unit testing frameworks. We categorize them
+ in 3 types :
+ </p>
+ <ol>
+ <li>
+ <strong>Type 1 : code logic unit testing</strong>. Probably the
+ best strategy for these tests is to use a
+ <link href="http://www.mockobjects.com";>Mock Objects</link> type
+ framework.
+ </li>
+ <li>
+ <strong>Type 2 : integration unit testing</strong>. Cactus is
+ typically in this category (I'll let you judge if it is the best or
+ not :)). These tests will exercise the interactions with the
+ container.
+ </li>
+ <li>
+ <strong>Type 3 : functional unit testing</strong>. These unit tests
+ will let you test the returned values from your server code. This is
+ for example
+ <link href="http://sourceforge.net/projects/httpunit";>HttpUnit
+ </link>.
+ </li>
+ </ol>
+ <p>
+ Ideally you would use 3 different frameworks just to unit test your
+ code ! Then you have to think about acceptance testing, system
+ integration testing, ...
+ </p>
+ <p>
+ Cactus was developed to fit Type 2 but also to be a very good
+ compromise for Type 1 and 3, with the idea that it is much easier to
+ have to write tests for a single framework than for several ! Moreover,
+ you can never fully test your code. We believe Cactus provides a middle
+ ground that provides a high confidence that your code will run when
+ deployed. However, it is your choice and you can use Cactus only for
+ Type 2 if you wish.
+ </p>
+
</s1>
<s1 title="Getting Started">
