Package net.sourceforge.groboutils.autodoc.v1.testserver

Abstract framework to aid subcomponents of the AutoDoc facility to interact between the JUnit testing suite and a implementation-specific server, which receives corrolated events from the AutoDoc and JUnit systems.

See:
Description

Interface Summary

Monitor	Monitors the state of multiple tests through the creation, retrieval, and sending to a server of the TestData for a specific test.
MonitorFinder	Generic interface in charge of discovering a specific pseudo-singleton type of Monitor.
Server	An interface which corresponds to a part of the framework that knows how to deal with the framework's TestData.
TestData	An interface used to briefly describe a test and the gathered data associated for the test in a particular framework.
TestDataFactory	A factory in charge of creating a specific TestData instance from a TestInfo unique identifier.
TestInfo	Information about a test which can uniquely identify a specific test.

Class Summary

AbstractWriterServer	An interface which corresponds to a part of the framework that knows how to deal with the framework's TestData.
DefaultMonitor	This implemenation of Monitor uses a Hashtable to store the test data.
DefaultTestData	A simple implementation of TestData which only knows about TestInfo.
DefaultTestInfo	An implementation of TestInfo which is specific to JUnit.
TestCorrelate	Helper method to aid in the use of Monitors and TestData.

Package net.sourceforge.groboutils.autodoc.v1.testserver Description

Abstract framework to aid subcomponents of the AutoDoc facility to interact between the JUnit testing suite and a implementation-specific server, which receives corrolated events from the AutoDoc and JUnit systems. This framework is itself not specific to JUnit, but it was designed with the JUnit-style events in mind.

Overview

This framework consists of six different classes which work together to allow for proper integration between JUnit and AutoDoc, and the implementation-specific "recorder", or server as it is referenced in this framework.

The Server interface is where the implementation-specific recorder receives data from the framework. It receives an event with framework-specific data, which has been collected over all the calls to the framework during a single JUnit test.

The Monitor interface handles the calls from both the JUnit and AutoDoc frameworks. It acts as a singleton for each JUnit test.

The MonitorFinder is a non-singleton which knows how to discover the pseudo-singleton Monitor, which is shared between the particular JUnit and AutoDoc framework instances.

The unit of test events is contained in the interface TestData. This is created by a TestDataFactory, a framework implementation specific factory in charge of creating TestData instances for the implementation classes to interact through.

The Monitor acts as a singleton for each individual test by having one TestInfo for each test, in order to uniquely identify the tests. The TestCorrelate abstract class provides functionality to create a TestInfo instance, and integrate it with the TestData through a MonitorFinder.