Revision as of 22:36, 13 January 2006

Getting the XSLT test suite

For example, on a Unix you might do

 env CVSROOT=:pserver:anoncvs@cvs.apache.org:/home/cvspublic cvs co xml-xalan/test

WARNING: these tests have only been checked in Seamonkey. They may well not work in Firefox.

In the tests directory in the Xalan tree you pulled (this is the directory that has conf and conf-gold as subdirectories) run the script found at content/xslt/tests/buster/helper/generate-rdf.pl in your source tree. This will generate a file called xalan.rdf in the Xalan tests directory.
Start a build that does NOT have the changes being tested in it. Go to the Tools > Web Development > Xalan Tests menu option.
Click the "Browse" button and browse for the xalan.rdf file that you created in step 1.
Select the "conf" item in the tree at the bottom of the Xalan Tests dialog.
Click "run checked tests"
Wait until the test completes. Then repeat steps 2-5 in a build that DOES have the changes being tested in it and compare the results.

@@ Line 10: / Line 10: @@
 = Running the tests =
-Follow the directions in [http://lxr.mozilla.org/seamonkey/source/content/xslt/tests/buster/ReadMe The XLST test README]
+WARNING: these tests have only been checked in Seamonkey.  They may well not work in Firefox.
+# In the <code>tests</code> directory in the Xalan tree you pulled (this is the directory that has <code>conf</code> and <code>conf-gold</code> as subdirectories) run the script found at <code>content/xslt/tests/buster/helper/generate-rdf.pl</code> in your source tree.  This will generate a file called <code>xalan.rdf</code> in the Xalan <code>tests</code> directory.
+# Start a build that does NOT have the changes being tested in it.  Go to the Tools > Web Development > Xalan Tests menu option.
+# Click the "Browse" button and browse for the <code>xalan.rdf</code> file that you created in step 1.
+# Select the "conf" item in the tree at the bottom of the Xalan Tests dialog.
+# Click "run checked tests"
+# Wait until the test completes.  Then repeat steps 2-5 in a build that DOES have the changes being tested in it and compare the results.