You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by mc...@apache.org on 2005/07/19 18:12:20 UTC
cvs commit: xml-xalan/test/java/xdocs/sources/tests xalanctests.xml run.xml overview.xml getstarted.xml faq.xml design.xml
mcnamara 2005/07/19 09:12:20
Modified: test/java/xdocs/sources/tests xalanctests.xml run.xml
overview.xml getstarted.xml faq.xml design.xml
Log:
Documentation updates for Xalan Java 2.7 release. This update also fixes
XALANJ-2129.
Revision Changes Path
1.3 +0 -2 xml-xalan/test/java/xdocs/sources/tests/xalanctests.xml
Index: xalanctests.xml
===================================================================
RCS file: /home/cvs/xml-xalan/test/java/xdocs/sources/tests/xalanctests.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- xalanctests.xml 27 Apr 2004 17:42:19 -0000 1.2
+++ xalanctests.xml 19 Jul 2005 16:12:20 -0000 1.3
@@ -24,8 +24,6 @@
<anchor name="how-to-run-c"/>
<s2 title="How-to: Run Xalan-C tests">
<p>In progress.</p>
- <p>Contact <jump href="paul_dick@lotus.com">Paul_Dick@lotus.com</jump> if you'd
- like to help in the Xalan-C API testing efforts.</p>
</s2>
<anchor name="ctesting-notes"/>
1.10 +2 -4 xml-xalan/test/java/xdocs/sources/tests/run.xml
Index: run.xml
===================================================================
RCS file: /home/cvs/xml-xalan/test/java/xdocs/sources/tests/run.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- run.xml 27 Apr 2004 17:42:19 -0000 1.9
+++ run.xml 19 Jul 2005 16:12:20 -0000 1.10
@@ -116,7 +116,7 @@
whatever data they can as results are generated; afterwards, we then
post-process the results into whatever presentation format is needed,
including perhaps re-calculating overall results (example: if we have
- a list of known fails correlated to Bugzilla numbers, then a stylesheet
+ a list of known fails correlated to JIRA numbers, then a stylesheet
could filter out these fails and report them as known bugs instead.
</p>
</s2>
@@ -187,12 +187,10 @@
<p>In progress. A few C++ API tests are checked into the <code>xml-xalan/c/Tests</code>
repository area already. To execute any set of 'conformance' tests with the
Xalan-C processor, we currently use the
- org.apache.qetest.xsl.<jump href="apidocs/org/apache/qetest/xsl/CConformanceTest.html">CConformanceTest</jump>
+ org.apache.qetest.xsl.<jump href="apidocs/org/apache/qetest/xsl/XalanCTestlet.html">XalanCTestlet</jump>
driver. This is written in Java to take advantage of the framework and
results reporting, but basically constructs a command line for each test
and then shells out to <code>TestXSLT.exe -in file.xsl...</code> to run the test;
it then uses the same validation routines as the Java ConformanceTest.</p>
- <p>Contact <jump href="paul_dick@lotus.com">Paul_Dick@lotus.com</jump> if you'd
- like to help in the Xalan-C API testing effort.</p>
</s2>
</s1>
\ No newline at end of file
1.10 +8 -6 xml-xalan/test/java/xdocs/sources/tests/overview.xml
Index: overview.xml
===================================================================
RCS file: /home/cvs/xml-xalan/test/java/xdocs/sources/tests/overview.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- overview.xml 27 Apr 2004 17:42:19 -0000 1.9
+++ overview.xml 19 Jul 2005 16:12:20 -0000 1.10
@@ -48,7 +48,9 @@
a rolled-up report of their pass/fail/other status. Our existing testing library includes
a wide array of tests, from XSLT conformance to detailed API tests, and welcomes
user-submitted tests as well. The 'smoketest' target (a subset of the most important
- tests) are also integrated into the <jump href="http://jakarta.apache.org/builds/gump">GUMP nightly build system</jump>, and thus ensure a
+ tests) are also integrated into the
+ <jump href="http://vmgump.apache.org/gump/public/xml-xalan/xml-xalan2-smoketest/index.html">GUMP nightly build system</jump>,
+ and thus ensure a
minimum baseline of functionality on a daily basis. Developers can run the smoketest
and ensure it passes before checking in code changes.</p>
</s2>
@@ -60,11 +62,11 @@
<label><code>xml-xalan/test</code></label>
<item>Top level dir for all Xalan versions/products tests</item>
<label></label>
- <label><code>xml-xalan/test/bin</code> (no longer included)</label>
- <item>All dependent .jar files, (including
- <jump href="http://jakarta.apache.org/ant/index.html">Ant</jump>
- and the Xerces parser) are included in the corresponding xml-xalan/java development
- tree</item>
+ <label><code>xml-xalan/test/tools</code></label>
+ <item>Tools required by the test harness, such as JTidy. Note that all .jars
+ required to run Xalan, including Ant, the Xerces parser, etc, are
+ included in the lib and tools directories under xml-xalan/java.
+ </item>
<label><code>xml-xalan/test/java/src</code></label>
<item>Java test automation source tree - this includes
a generic testing framework as well as specific API tests for parts of Xalan
1.8 +4 -9 xml-xalan/test/java/xdocs/sources/tests/getstarted.xml
Index: getstarted.xml
===================================================================
RCS file: /home/cvs/xml-xalan/test/java/xdocs/sources/tests/getstarted.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- getstarted.xml 27 Apr 2004 17:42:19 -0000 1.7
+++ getstarted.xml 19 Jul 2005 16:12:20 -0000 1.8
@@ -92,15 +92,10 @@
</p><p>To download Xalan builds, see the:
<jump href="http://xml.apache.org/xalan-j/dist/">Xalan-J download page</jump> or the
<jump href="http://xml.apache.org/xalan-c/dist/">Xalan-C download page</jump>
- </p><p>To get the test sources, do either of the following:
+ </p><p>To get the test sources, do the following:
<br/>Check out the xml-xalan\test repository <jump href="http://xml.apache.org/cvs.html">directly from CVS</jump>
- (<jump href="http://xml.apache.org/cvs.html">read-only access</jump> is available to all), or:
- <br/><br/>Get the latest <jump href="http://xml.apache.org/from-cvs/xml-xalan/">dev-snapshot</jump>:
- these are .tar.gz files of the entire xml-xalan repository, including both the
- development sources and the test sources (they are just source, however, and are not prebuilt), or:
- <br/><br/>Get the latest <jump href="http://xml.apache.org/xalan-j/dist/nightly/">GUMP build output</jump>:
- which includes full compiled distribution builds as well as a full set of
- prcompiled tests and test results in a *smoketest.tar.gz file.
+ (<jump href="http://xml.apache.org/cvs.html">read-only access</jump> is available to all).
+ <br/><br/>
</p>
</s2>
@@ -109,7 +104,7 @@
<s2 title="Building the Tests">
<p>Since the test automation is written in Java, you must build it before running
any tests. Like Xalan-J, we use Ant build.xml files as 'makefiles' to build the
- project. A copy of the Ant runtime files is provided in the xml-xalan/java/bin directory if you
+ project. A copy of the Ant runtime files is provided in the xml-xalan/java/tools directory if you
need them; you may also use your own copy of Ant if you have it installed.
Unless specifically noted, all testing code should work either on Windows or
UNIX systems; adjust .sh/.bat and path\separators/as needed. Note that paths
1.6 +1 -1 xml-xalan/test/java/xdocs/sources/tests/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/xml-xalan/test/java/xdocs/sources/tests/faq.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- faq.xml 27 Apr 2004 17:42:19 -0000 1.5
+++ faq.xml 19 Jul 2005 16:12:20 -0000 1.6
@@ -181,7 +181,7 @@
see debugconf.properties for settable options. Note that this method does not
directly support 'conf.one' to run only a <b>single</b> test.<br/></li>
<li>Setup everything manually. Minimal setup is: CLASSPATH has
- xalan.jar;xercesImpl.jar;xml-apis.jar;testxsl.jar, command line parameters or
+ xalan.jar;serializer.jar,xercesImpl.jar;xml-apis.jar;testxsl.jar, command line parameters or
-load file.properties includes other test properties, like inputDir, goldDir,
outputDir, logFile, etc.</li>
</ul>
1.7 +0 -2 xml-xalan/test/java/xdocs/sources/tests/design.xml
Index: design.xml
===================================================================
RCS file: /home/cvs/xml-xalan/test/java/xdocs/sources/tests/design.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- design.xml 27 Apr 2004 17:42:19 -0000 1.6
+++ design.xml 19 Jul 2005 16:12:20 -0000 1.7
@@ -211,8 +211,6 @@
</gloss>
<p>Please: if you plan to submit Java API tests, use the existing framework
as <link idref="submit" anchor="write-API-tests">described</link>.</p>
- <p>Contact <jump href="paul_dick@lotus.com">Paul_Dick@lotus.com</jump> if you'd
- like to help in the Xalan-C API testing effort.</p>
</s2>
<anchor name="standards-xsl-tests"/>
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-cvs-help@xml.apache.org