Re: Even more test code

On Fri, Apr 27, 2001 at 12:15:16AM -0500, Sam TH wrote:
> Ok, in additon to the changes mentioned in my last email, this has
> even more new code.

A diff to the README file to go along with the new code.

Index: README
===================================================================
RCS file: /cvs/subversion/subversion/tests/clients/cmdline/README,v
retrieving revision 1.3
diff -u -r1.3 README
--- README 2001/04/25 21:23:15 1.3
+++ README 2001/04/27 05:23:06
@@ -19,8 +19,8 @@
 ---------------------------
 
 The point of this test system is that it's *automated*: that is, each
-test can algoritmically verify the results and indicate "PASS" or
-"FAIL".
+test can algoritmically verify the results and indicate the status of
+the test.
 
 We've identified two broad classes of verification:
 
@@ -98,7 +98,30 @@
        "subdir:".
 
 
+Result Reporting
+----------------
 
+Since not all bugs in Subversion are yet fixed, there are some tests
+in the test suite that are expected to fail. Therefore, the automated
+tester can report any one of four different results for a given test.
+
+ * PASS: The test was expected to pass, and it passed. This is the
+ state most tests should be in.
+
+ * FAIL: The test was expected to pass, but it failed. This class of
+ results should be as small as possible.
+
+ * XPASS: The test was expected to fail, but it passed. This could
+ mean that the bug was fixed by a recent change, or that the test
+ suite is buggy.
+
+ * XFAIL: The test was expected to fail, and it failed. This is the
+ status for tests verifying currently open bugs, for example.
+
+[NB: The inconsistency of the naming (XFAIL is an expected result, but
+XPASS is an unexpected result) is due to historical precedent in
+previous testing frameworks.]
+
 ------------------------------------------------------------------
 
 The files in this directory, grouped by function:
@@ -107,6 +130,8 @@
  * svn_test_main.py: main test framework.
                           exports client_test(), which runs a list of
                              provided tests.
+ also contains many shared routines useful
+ for the entire suite.
 
  * example_tests1.py: template test script.
                           demonstrates how to write tests and then
@@ -114,13 +139,13 @@
  -----
 
  * svn_tree.py: infrastructure for SVNTreeNode class,
- tree constructors, tree comparison routines.
+ tree constructors, tree comparison routines.
+ also routines for generating trees from svn
+ output and on-disk working copies.
 
- * svn_output.py: routines to parse subcommand output into
- specific kinds of trees.
+ * svn_entry.py: code for parsing SVN/entries files and
+ generating trees from them.
 
- * svn_wc.py: routines to parse a working copy (and
- entries files) into specific kinds of trees.
  -----
 
  * local_tests.py: tests: client operations using ra_local.
@@ -128,4 +153,5 @@
  * dav_tests.py: tests: client operations using ra_dav
 
  * xml_tests.py: tests: client operations to/from XML.
-
+
+ * bug_tests.py: tests: current and former bugs from IssueZilla

           
sam th --- sam_at_uchicago.edu --- http://www.abisource.com/~sam/
OpenPGP Key: CABD33FC --- http://samth.dyndns.org/key
DeCSS: http://samth.dynds.org/decss