summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBen Kaduk <kaduk@mit.edu>2012-10-02 18:03:16 -0400
committerBen Kaduk <kaduk@mit.edu>2012-10-08 15:01:42 -0400
commitfd136728de5b603974e3ec21bc5856406c4e814d (patch)
tree1335b87c08878046d800d09abb17e8f293989cee
parent0a735e18e1e9d4e3f25fd04dad841221e5d5d46a (diff)
downloadkrb5-fd136728de5b603974e3ec21bc5856406c4e814d.tar.gz
krb5-fd136728de5b603974e3ec21bc5856406c4e814d.tar.xz
krb5-fd136728de5b603974e3ec21bc5856406c4e814d.zip
Document DejaGnu dependency and manual tests
The Texinfo install guide had a separate subsection about the DejaGnu tests which did not get converted to the RST source. In the testing section, also link to the wiki page on manual testing. ticket: 7407
-rw-r--r--doc/rst_source/krb_build/doing_build.rst11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/rst_source/krb_build/doing_build.rst b/doc/rst_source/krb_build/doing_build.rst
index 8617a1c3e..bc438c849 100644
--- a/doc/rst_source/krb_build/doing_build.rst
+++ b/doc/rst_source/krb_build/doing_build.rst
@@ -137,6 +137,10 @@ However, there are several prerequisites that must be satisfied first:
the test suite. This often means passing **-**\ **-with-tcl** to
configure to tell it the location of the Tcl configuration
script. (See :ref:`options2configure`.)
+* In addition to Tcl, DejaGnu must be available on the system for some
+ of the tests to run. The test suite will still run the other tests
+ if DejaGnu is not present, but the test coverage will be reduced
+ accordingly.
* On some operating systems, you have to run ``make install`` before
running ``make check``, or the test suite will pick up installed
versions of Kerberos libraries rather than the newly built ones.
@@ -149,6 +153,13 @@ However, there are several prerequisites that must be satisfied first:
the portmap daemon and it has to be listening to the regular network
interface (not just localhost).
+There are additional regression tests available, which are not run
+by ``make check``. These tests require manual setup and teardown of
+support infrastructure which is not easily automated, or require
+excessive resources for ordinary use. The procedure for running
+the manual tests is documented at
+http://k5wiki.kerberos.org/wiki/Manual_Testing.
+
Cleaning up the build
---------------------