| Package Name | Comment |
| csdl.foo | |
| csdl.jblanket |
Contains the parent class describing the implementation for the
ClassModifier and JBlanketReport classes in the modify and report packages,
respectively.
|
| csdl.jblanket.ant |
Contains the Task definitions for running JBlanket with Apache Ant.
|
| csdl.jblanket.app |
Provides the application used to exclude individual methods from the coverage
measurement. The System's package structure is mapped into a tree and
displayed in a window. The user is able to double-click on the package or
class names to expand the nodes. To exclude methods, the user must first
select a node and then click on the "Exclude" button. The button will change
all of the methods under the selected node to the appropriate color. If a
user excluded method is to be included again, the user must first select the
method node or its parent and click on the "Include" button. This will
return the node to its original color or the untested color if it was
originally an excluded method.
|
| csdl.jblanket.app.tree |
Provides the specific classes used to create, modify and store the tree
structure used to represent the analyzed system.
|
| csdl.jblanket.methodset |
MethodSet is a simple, persistent ADT that represents a container of
information regarding Methods. Each Method is represented by a set
of strings that provide information regarding the package and class
membership of the Method, as well as an ordered list of the class
signatures of its parameters.
MethodSets are used by JBlanket to record
- all methods being measured
- all methods not being measured
- all methods invoked at run-time during testing of a system
The difference between the first, second, and third lists is the set of
methods in a system that were not exercised through testing, i.e. the
method coverage.
|
| csdl.jblanket.modifier |
Contains the classes used during method instrumentation.
Java methods are modified such that their type signatures are stored in XML
files when they are invoked. Modifiable methods include non-abstract and
non-native methods. Constructors or methods containing one line of source
code can also be excluded from coverage to measure XC.
Byte code in .class or .jar files can be instrumented. When modifying .class
files, packages or individual classes can be either included or excluded.
When modifying JAR files, either all packages or specific package
may be included by specifying a package prefix.
In addition, all methods to be included in the coverage measurement are
counted. These methods are later compared against those methods that are
invoked during testing to calculate method coverage.
|
| csdl.jblanket.report |
Contains the classes to format JBlanket output.
The raw JBlanket results stored in XML files are aggregated into one file
according to class and type of method (constructor, oneline, tested, or
untested methods). This file is then parsed and formatted into HTML web pages
using XSLT. Because test cases are implemented using JUnit, the report
from JBlanket is formatted using a stylesheet similar to the one used by
JUnit (from Apache Ant).
|
| csdl.jblanket.report.element |
Contains the classes to create aggregate XML file.
The JBlanket results are stored in XML files testedMethods.xml and
diffMethods.xml, and optional files onelineMethods.xml and
constructorMethods.xml, are aggregated into one file ('COVER-MethodSets.xml')
according to class and category of method (tested, untested, oneline, or
constructor).
|
| csdl.jblanket.util |
Contains the utility classes for JBlanket. These classes include:
- Factory to package or extract JAR files
- Constants used throughout JBlanket
- Container for all JBlanket method categories
- JBlanket version information
|
| csdl.stackmvc.control | |
| csdl.stackmvc.control.command | |
| csdl.stackmvc.model | |
| csdl.stackmvc.util | |