1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
<HTML><HEAD><TITLE>net.sourceforge.groboutils.autodoc.v1.testserver</TITLE></HEAD><BODY>
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.
<!-- A bit redundant. Need to freshen this description when I get a chance to
really think about it. -->
<H3>Overview</H3>
<P>
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 <i>server</i> as it is referenced in this
framework.
</P>
<P>
The <tt>Server</tt> 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.
</P>
<P>
The <tt>Monitor</tt> interface handles the calls from both the JUnit and AutoDoc
frameworks. It acts as a singleton for each JUnit test.
</P>
<P>
The <tt>MonitorFinder</tt> is a non-singleton which knows how to discover the
pseudo-singleton <tt>Monitor</tt>, which is shared between the particular JUnit
and AutoDoc framework instances.
</P>
<P>
The unit of test events is contained in the interface <tt>TestData</tt>. This
is created by a <tt>TestDataFactory</tt>, a framework implementation specific
factory in charge of creating <tt>TestData</tt> instances for the implementation
classes to interact through.
</P>
<P>
The <tt>Monitor</tt> acts as a singleton for each individual test by having one
<tt>TestInfo</tt> for each test, in order to uniquely identify the tests.
The <tt>TestCorrelate</tt> abstract class provides functionality to create a
<tt>TestInfo</tt> instance, and integrate it with the <tt>TestData</tt> through
a <tt>MonitorFinder</tt>.
</P>
</BODY></HTML>
|
