<?xml version="1.0" encoding="ISO-8859-1"?>
<!--
version $Date: 2004/01/09 20:32:27 $

-->
<list>
    <category name="Testing">
        <project>
            <name>testing-junit</name>
            <part>JUnit helpers and extentions</part>
            <package>net.sourceforge.groboutils.junit.v1</package>
            <description>
            JUnit extentions for easing test making.
            </description>
            <class>
                <name>AssertConstructor</name>
                <description>
                Similar to the Assert class in JUnit, but allows for testing
                objects and classes for the existence of different
                constructors.
                </description>
            </class>
            <class>
                <name>AssertTestFactory</name>
                <description>
                Creates Test objects that execute a single assert.  Used to
                create 'soft' (sub) tests during integration testing.
                </description>
            </class>
            <class>
                <name>SubTestTestCase</name>
                <description>
                Subclass of TestCase that allows for a test to dynamically
                register a sub-test, which will be run after the owning test
                finishes, and in new tests.
                </description>
            </class>
            <class>
                <name>IntegrationTestCase</name>
                <description>
                Subclass of TestCase designed for integration tests, which
                generally need 'soft' failures - a failure which does not need
                to stop the execution of the test.
                </description>
            </class>
            <class>
                <name>MultiThreadedTestRunner</name>
                <description>
                A utility class which executes a collection of small test
                methods in parallel. Capable of specifying a maximum run time
                to prevent dead-locks or infinite loops from hanging the test
                execution. Propigates all errors to the owning class.
                </description>
            </class>
            <class>
                <name>SysPropertiesUtil</name>
                <description>
                Utility that allows for easy setting and reseting of System
                properties.  Some classes that need testing may depend upon a
                System property setting, and this class will help testing that.
                This is JDK 1.1 and above compatible.
                </description>
            </class>
            <status>
            17-Jul-2003:
            Updates to MultiThreadedTestRunner allow for monitors to check
            the status of runners without needing to quit, and added the
            ability to kill wild threads.  The documentation for this has
            been updated as well.
            </status>
        </project>
        <project>
            <name>testing-junit</name>
            <part>Test Class Parsing</part>
            <package>net.sourceforge.groboutils.junit.v1.parser</package>
            <description>
            Extracted the functionality used by
            <tt>junit.framework.TestSuite</tt> to parse the Test classes, and
            enabled it for easy exension to support different construction
            mechanisms.
            </description>
            <status>
            17-Jul-2003:
            This is fairly stable, but the code coverage reports show that
            it needs a bit more testing in some areas.
            </status>
        </project>
        <project>
            <name>testing-junit</name>
            <part>Hierarchial Unit Tests</part>
            <package>net.sourceforge.groboutils.junit.v1.iftc</package>
            <description>
             JUnit extention for helping in the creation of hierarchial test
             cases, also known as 'contract' or 'interface' test-cases.
            </description>
            <status>
            10-Jan-2004:
            Found and fixed a minor bug with passing the message on an
            assert in IntegrationTestCase.
            </status>
        </project>
    </category>
</list>

