Patch to procedures.txt describing how to run the test suite

Russ Allbery rra at stanford.edu
Sun Aug 6 21:06:55 EDT 2006


I promised to write something like this up a while back and finally got to
it.  Could others look this over and let me know if it's correct enough to
be a starting point?  If so, I'll commit it.

Index: procedures.txt
===================================================================
--- procedures.txt	(revision 18327)
+++ procedures.txt	(working copy)
@@ -22,6 +22,32 @@
 change to the release branch and set the "version_fixed" keyword on
 the ticket.
 
+RUNNING THE TEST SUITE
+======================
+
+To run the test suite on Unix, run "make check" from the top of the source
+tree.  However, there are several prerequisites that need to be satisfied
+first:
+
+ * Configure and build Kerberos with Tcl support.  Tcl is used to drive
+   the test suite.  This often means passing --with-tcl to configure to
+   tell it the location of the Tcl configuration script.
+
+ * You have to run make install before running make check, or the test
+   suite will often pick up the installed version of Kerberos rather than
+   the newly built one.  You can install into a prefix that isn't in the
+   system library search path, though.  This theoretically could be fixed
+   with the appropriate environment variable magic in the test suite, but
+   hasn't been yet.
+
+ * In order to test the RPC layer, the local system has to be running
+   the portmap daemon and it has to be listening to the regular network
+   interface (*not* just localhost).
+
+In order to fully test the appl tree, you will need to add entries to the
+.k5login for the user running the test suite and the root user on the
+system.  These tests will be skipped if that configuration is missing.
+
 USING Subversion COMMITS TO CREATE/UPDATE RT TICKETS
 =============================================
 

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>



More information about the krbdev mailing list