Lecture Notes in Computer Science 3472

428 Axel Belinfante, Lars Frantzen, and Christian Schallhart
use wildcards to specify abstract test purposes which are completed by the tool
in every possible way to allow abstraction from event-ordering. AGEDIS offers
five predefined strategies to generate test purposes:
• Random test generation
• State coverage – ideally cover all states of the specification
• Transition coverage – ideally cover all transitions of the specification
• Interface coverage – ideally cover all controllable and observable interface
elements
• Interface coverage with parameters – like interface coverage with all parameter
combinations
The abstract specification parts like classes, objects, methods and data types
have to be mapped to the SUT. This, and the test architecture itself, is described
in an XML schema which instantiates the test execution directives interface.
The model execution interface encodes all the behavior models of the SUT,
i.e. the classes, objects and state machines. Again IF is used to do so. See also
here the web site for a detailed description.
Both the abstract test suite and test suite traces are described by the same
XML schema. A test suite consists of a set of test cases, zero or more test suite
traces and a description of the test creation model. Each test case consists of a
set of test steps which in turn may consist of stimuli (method calls), observations,
directions for continuation or verdicts. Several stimuli may occur in one test step
and they can be executed sequentially or in parallel. The common verdicts pass,
fail and inconclusive are possible. Alternative behavior within a test case is used
to model nondeterminism. Test cases can also be parameterized to be run with
different values and other test cases can be evoked within a test case. AGEDIS is
restricted to static systems, i.e. objects can not be created or destructed during
test case execution.
The AGEDIS tools are written in Java. Currently, the specification modeling
in AML and the creation of test generation directives are only supported using
the commercial Objecteering UML Editor together with an AML profile. The
designed model can be simulated with an IF-simulator. Test generation based
on the model and the test generation directives is done by the TGV algorithms.
AGEDIS also allows an execution of the generated test suite. The execution
framework is called Spider. It is able to execute test cases on distributed components
written in Java, C or C++. Spider takes care of the distribution of the
generated test objects. Furthermore it controls the whole test run, i.e. providing
synchronous or asynchronous stimuli, observing the outputs, checking them
against the specification and writing the generated traces in the suite as XML
files. Two tools are provided for test analysis, a coverage and a defect analyzer.
The first one checks for uncovered data value combinations and method calls.
It generates new test cases to cover these missed parts and a coverage analysis
report. The defect analyzer tries to cluster traces which lead to the same fault
and generates one single fault-trace out of them to ease the analysis when many
faults are detected.