curcuru 01/03/01 16:51:52
Modified: test/java/src/org/apache/qetest package.html
test/java/src/org/apache/qetest/xsl package.html
Log:
Basic documentation updates; brief description of new Testlets stuff
Revision Changes Path
1.2 +11 -3 xml-xalan/test/java/src/org/apache/qetest/package.html
Index: package.html
===================================================================
RCS file: /home/cvs/xml-xalan/test/java/src/org/apache/qetest/package.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- package.html 2000/11/01 23:30:51 1.1
+++ package.html 2001/03/02 00:51:49 1.2
@@ -30,9 +30,14 @@
Properties block to sub-objects or contained objects for
their own initializations. One future drawback: need to
ensure the namespace doesn't have collisions between tests,
- reporters, and loggers.</li>
+ reporters, and loggers. Eventually I'd like to have a
+ 'namespace' for just the tests themselves.</li>
<li>Test, TestImpl, FileBasedTest: these all provide structure
and utility methods useful for testing in general.</li>
+ <li>Testlet, Datalet: these small, focused mini-tests
+ that encourage creating data driven tests and allow you
+ to separate the specific testing algorithim used from
+ the set of data to execute it on.</li>
<li>User subclasses of the Test classes should simply focus on
manipulating the product under test and calling log*() or check*()
methods to report information. They shouldn't worry about the
@@ -51,12 +56,15 @@
<li>CheckService is a generic service for checking 'equivalence'
of two objects and reporting the pass/fail/other result thereof.
A SimpleFileCheckService implementation is provided as an
- example.</li>
+ example; we have plans to add various other kinds of checkers,
+ perhaps a DOMCheckService.</li>
<li>OutputNameManager is a cheap-o helper for tests that create
a large number of consecutive output files.</li>
<li>TestfileInfo is a simple data-holding class to store info
about a test data file. It is used in FileBasedTest, which may
- be a useful base class for your tests.</li>
+ be a useful base class for your tests. This should probably be
+ replaced with a Datalet which, along with Testlets, provides a
+ lighter-weight way to write tests.</li>
</ul>
</body>
</html>
1.2 +14 -5
xml-xalan/test/java/src/org/apache/qetest/xsl/package.html
Index: package.html
===================================================================
RCS file:
/home/cvs/xml-xalan/test/java/src/org/apache/qetest/xsl/package.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- package.html 2000/11/01 23:26:57 1.1
+++ package.html 2001/03/02 00:51:51 1.2
@@ -21,11 +21,12 @@
the HTML parsing is unimplemented - we need a good HTML->DOM
parser we can use in Apache - any suggestions?</li>
<li>XSLTestfileInfo - simple extension of TestfileInfo to
- add xmlName member.</li>
+ add xmlName member. Should be replaced with StylesheetDatalet</li>
<li>XSLDirectoryIterator - simple implementation that processes
xsl/xml file pairs from a fileList or over a directory tree,
automatically comparing the result files with a known good
- or 'gold' reference tree of outputs.</li>
+ or 'gold' reference tree of outputs. Should be replaced
+ with StylesheetTestletDriver and various Testlets.</li>
<li>XSLProcessorTestBase - adds useful XSLT processing
utilities, etc. from FileTestBase: including flags like
-preprocess, -flavor, -category, etc. Most xsl and trax
@@ -34,13 +35,21 @@
<ul>Current tests include:
<li>ConformanceTest - generic test driver, including some
FilenameFilters. This essentially uses the XSLDirectoryIterator
- for everything.</li>
+ for everything.
+ Being replaced by StylesheetTestletDriver and
+ StylesheetTestlet/Datalet</li>
<li>PerformanceTest - test driver that iterates repeatedly and
- reports memory and timing info.</li>
+ reports memory and timing info
+ Being replaced by StylesheetTestletDriver and
+ PerformanceTestlet, PerfPreloadTestlet</li>
+
<li>CConformanceTest - generic test driver that constructs a
command line and then shells out to execute TestXSLT.exe, which
is from the Xalan-C build. This allows basic comparisons of
- results from the Java versions with the C++ versions.</li>
+ results from the Java versions with the C++ versions.
+ I'd like to replace this with a more generic and configurable
+ CmdlineTestlet, that can run any sort of command-line interface
+ like this in a standard way.</li>
</ul>
</body>
</html>
