ArbitraryParameterEnumerator |
Implementations of this class are used to provide an enumeration of all available arbitrary parameters for a fixture
class in Eclipse while test scripts are being edited.
|
ArbitraryParameterFixture |
Interface for fixtures that allow for arbitrary, non-predetermined parameters to be specified.
|
CustomComparatorAndConversionFixture |
This fixture extends the CustomComparatorFixture by a means to manually determine the target type to which
the expected result in a test script is to be converted.
|
CustomComparatorFixture |
A custom comparator fixture overrides the default "equals" comparator that is used to compare actual and expected
results.
|
CustomProposalFixture |
Marker interface to denote fixtures which have a counterpart (implementation of CustomProposalProvider ) that
provides proposals for parameters of that fixture.
|
CustomProposalProvider |
Implementations of this interface are used by Integrity inside Eclipse to determine proposals for parameter values.
|
CustomStringConversionFixture |
A fixture may implement this optional interface to provide customized string conversion functionality, which will be
used to convert values returned by the fixture to strings to be displayed in the console or the XML result file.
|
ExtendedResultFixture |
Fixtures can implement this optional interface to provide additional result information after the main fixture method
call(s) have been performed.
|
FinalizationTestFixture |
A finalization test fixture defines a method that is to be invoked AFTER the actual fixture methods had been called
during a tabletest invocation.
|
FixtureInstanceFactory<C> |
Fixture Factories can be used to customize fixture instantiation.
|
ResultAwareFixture |
A fixture implementing this interface is notified by Integrity in advance of calling a fixture method, thereby
telling the fixture instance about the (named) results that will be checked after the upcoming fixture method call
has returned its result.
This knowledge is usually not required by a fixture - it is simply intended to deliver all available result data,
even though the test script author might not use all possible (named) results during a test invocation.
|