All Classes and Interfaces

Class
Description
ClientDataContext implementation which is used by the test framework.
Set of constants to be used and shared in the test framework implementation classes.
Base implementation of an ExtractionPluginProcessor, which simply delegates the ExtractionPluginProcessor.process(ClientTrace, ClientDataContext) call to the given ExtractionPlugin.
Extension to the DefaultPluginResultGenerator which also writes each data stream of a Trace to a separate file (see Trace.setData(String, DataWriter)).
Extension to the DefaultResultValidator which also validates each data stream of a Trace by comparing to each expected file containing a data stream of that type (see DefaultPluginResultGenerator and Trace.setData(String, DataWriter).
Utility methods for deserializing the input of an ExtractionPlugin, for use in the Flits test framework.
Base implementation of the Flits framework, for use with embedded deferred extraction plugins.
Base implementation of the Flits framework, for use with embedded extraction plugins.
Base class for Extraction Plugin tests using the Flits framework.
Base implementation of the Flits framework processor, for use with external extraction plugins.
This utility class contains some functions to format HQL based logging.
Validator which fully serializes the Trace to a JSON file using a given TraceToJson, and compares it line by line to a single input file.
 
Utility functions for use when running an ExtractionPluginProcessor.
A RandomAccessData implementation which reads from an in-memory byte array.
Base implementation of the Flits framework, for use with remote extraction plugins.
 
 
Simple ClientDataContext which has a data type and an accompanying data sequence, used for the input of a Flits run.
Exception type to indicate exceptions that are related test input (test files, or plugin).
 
 
Simple Trace and ClientTrace implementation used as input for a Flits framework test run.
 
Utility class for creating a JSON representation of traces.