<?xml version="1.0" encoding="ISO-8859-1"?>
<document>
<head>
    <name>Welcome</name>
    <doc-version>$Date: 2004/04/17 08:24:40 $</doc-version>
</head>
<body>
    <P>
    The CodeCoverage package contains a tool to help you discover what
    parts of your code have not executed during unit tests.
    </P>
    <P>
    You can find an article on the various code-coverage techniques in the
    <a href="http://www.bullseye.com/coverage.html">on-line article by Steve
    Cornet at Bullseye Testing Technology</a>.
    </P>
    <toc>
        <LI><link name="getting_started">Getting Started with GroboCoverage</link></LI>
        <LI><link name="advanced_users">Advanced usage of GroboCoverage</link></LI>
        <LI><link name="v2_antdoc">Detailed Ant task documentation</link>
            <UL>
                <LI><link name="v2_antdoc_grobo-instrument">grobo-instrument</link></LI>
                <LI><link name="v2_antdoc_grobo-report">grobo-report</link></LI>
                <LI><link name="v2_antdoc_grobo-rezip">grobo-rezip</link></LI>
                <LI><link name="v2_antdoc_coveragepostcompile">coveragepostcompile</link> <I>(deprecated)</I></LI>
                <LI><link name="v2_antdoc_coveragereport">coveragereport</link> <I>(deprecated)</I></LI>
            </UL>
        </LI>
        <LI><link name="complex_setup">Integrating GroboCoverage with
        complex build environments</link></LI>
        <LI><link name="whats_new">What's new</link></LI>
        
        <li-toc>Documents you may not care about
            <LI><link name="requirements">Requirements</link></LI>
            <LI><link name="v2_design">Design</link></LI>
            <LI><link name="v1_design">Original Design</link> (for those
            who want to know about alternatives to BCEL-based code-coverage
            solutions)</LI>
        </li-toc>
    </toc>
    
    <summary />
</body>
</document>

