Javadoc Overview
The source code for the Blitz system is organized into
several packages. The contents of each package are summarized here;
details can be found in the Javadoc itself.
| Package Name |
Contents |
blitz.main |
Provides the public API for the Blitz
system. This includes the primary entry points for all execution; it
also includes the interfaces that are required by all users of the code
as well as by the Blitz class itself. |
blitz.exception |
Provides implementations for all exceptions that are
likely to be encountered. |
blitz.entity |
Provides the TestCase, TestSuite,
and TestScenario implementation classes in support of the
public API. |
blitz.matcher |
Provides basic implementations of the IMatcher
interface. |
blitz.filter |
Provides basic implementations of the IFilter
interface. |
blitz.concurrency |
Provides implementation classes that enable concurrent
execution of tests. |
blitz.outcome |
Provides implementations for the IOutcome
interface, which are used by Blitz for recording the
outcomes of tests. |
TOP
| Package Name |
Contents |
blitz.util.constant |
Provides a single class of constant definitions. |
blitz.util.operation |
Provides specific types of centralized functionality
that is used throughout the Blitz system. |
blitz.util.trace |
Provides classes which create execution path traces. |
TOP
| Package Name |
Contents |
blitz.xml.content |
Provides a number of relatively simple "content"
objects which are used in the HashMap representation of a
test. The "content" objects are used in place of simple strings so as to
disambiguate content types in situations where more than one content
type is permitted. |
blitz.xml.io |
Provides implementation classes with functionality to
validate, parse, read and write XML test files, and convert them into
appropriate test objects. |
blitz.xml.validation |
Provides an implementation class with functionality to
schema-validate XML-based test files. |
TOP
| Package Name |
Contents |
blitz.ui.dialog |
Provides several dialogs that are used for specialized
types of input. |
blitz.ui.editor |
Provides classes which are used for visually editing
various different kinds of data: test cases, test suites, test
scenarios, expected result files, property files, and simple text files. |
blitz.ui.list |
Provides classes which implement specialized display
lists that are capable of holding heterogeneous objects. |
blitz.ui.resource |
Provides functionality for managing resources in the
UI. |
blitz.ui.support |
Provides classes which provide supporting functionality
to the other UI classes. |
blitx.ui.viewer |
Provides classes to allow viewing (but not editing) of
certain types of files. |
TOP
| Package Name |
Contents |
blitz.example |
Provides sample code that implements the requirements
for an operative. |
TOP
|
REVIOUS
OME