Borland® Gauntlet™ 2007 Diagnostics Option Release Notes
Version 1.1
August 31, 2007
This file contains important information about Gauntlet Diagnostics.
Read this file in its entirety.
Features
Gauntlet Diagnostics is an optional premium feature in Gauntlet that enables you to monitor code coverage statistics in the Gauntlet Dashboard. It provides the following features:
- Traces code-test coverage for modules or packages and displays the number of source lines and the percentage of lines, classes, and methods exercised in the code.
- Tracks code coverage trends across projects, modules, or packages and displays results in the dashboard Test To Code page.
- Provides drill-down granularity to the method level to facilitate more comprehensive monitoring of code coverage.
- Graphs the coverage statistics and presents them in line charts in the Test To Code page.
- Reports the least-covered packages.
Top
Prerequisites
Following are the system requirements for installing and running the
Gauntlet Diagnostics Option.
- Gauntlet 1.0 or later must be installed.
- JRE 1.5 or later must be installed.
Top
Known Issues
The following are known issues in the Gauntlet Diagnostics option:
- There are no known issues at this time.
Top
License Installation Instructions
Use the following instructions to install the Gauntlet Diagnostics premium license:
- On the Gauntlet server, open the Gauntlet Dashboard, click Administration on the toolbar, and then click License in the menu tree.
The current License information appears.
- Click Upload License.
The Update Gauntlet License dialog box opens.
- Click Browse and navigate to the location where you saved the Gauntlet Diagnostics policy file; select the file to complete the Filename field, and then click Upload.
- Review the license information that appears.
- Click Combine to apply the new settings from the uploaded file.
- Close the Gauntlet Dashboard and then stop and restart Gauntlet.
The new settings appear when you reopen the Gauntlet Dashboard and view the license settings.
For more information about using the Gauntlet license facility, see Configuring Gauntlet Licenses in the Gauntlet online help or user guide.
Top
Gauntlet Diagnostics enables a Test To Code page in the Gauntlet Dashboard to display code coverage details. Using Gauntlet's Ant build process to get code coverage in your Java-compile environment requires that you modify the build.xml file to include the appropriate JVM attributes for the Ant task.
To enable the code coverage results to display in the Gauntlet Dashboard, do the following:
- Open the build.xml file.
- Add the following statement to the build file.
<javac srcdir="${src}" destdir="${classes}" debug="true" debuglevel=”lines,source”>
- Save your changes to the build file.
Note: The debuglevel setting (lines,source) is required by the Gauntlet opticc code to render the code coverage detail in the user interface. Gauntlet shows line coverage data in the Gauntlet Dashboard.
Top
Copyright © 2007
Borland Software Corporation. All Borland brand and product names are trademarks
or registered trademarks of Borland Software Corporation in the United States
and other countries. All other marks are the property of their respective
owners.