BIND 10 trac1213, updated. 4a843f9058e625685cf2338fe89c9a89af3c1777 [1213] Final tidy-up pending initial review.

[BIND 10 source code commits]

The branch, trac1213 has been updated
       via  4a843f9058e625685cf2338fe89c9a89af3c1777 (commit)
      from  5275b7b65e2ce2acf92528868c9859dd4407c4c1 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 4a843f9058e625685cf2338fe89c9a89af3c1777
Author: Stephen Morris <stephen at isc.org>
Date:   Fri Oct 7 12:16:39 2011 +0100

    [1213] Final tidy-up pending initial review.

-----------------------------------------------------------------------

Summary of changes:
 tests/system/conf.sh.in  |    6 ++-
 tests/system/ixfr/README |   70 +++++++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 73 insertions(+), 3 deletions(-)

-----------------------------------------------------------------------
diff --git a/tests/system/conf.sh.in b/tests/system/conf.sh.in
index e5203a8..37483e8 100755
--- a/tests/system/conf.sh.in
+++ b/tests/system/conf.sh.in
@@ -51,8 +51,10 @@ export RNDC=$BIND9_TOP/bin/rndc/rndc
 export TESTSOCK=$BIND9_TOP/bin/tests/system/testsock.pl
 export DIGCOMP=$BIND9_TOP/bin/tests/system/digcomp.pl
 
-export SUBDIRS="bindctl glue ixfr/in-1 ixfr/in-2"
-#SUBDIRS="dnssec masterfile xfer"
+export SUBDIRS="bindctl glue"
+# Add appropriate subdirectories to the above statement as the tests become
+# available.
+#SUBDIRS="dnssec masterfile ixfr/in-1 ixfr/in-2 ixfr/in-2 ixfr/in-4"
 
 # PERL will be an empty string if no perl interpreter was found.  A similar
 # comment applies to AWK.
diff --git a/tests/system/ixfr/README b/tests/system/ixfr/README
index 44f44e6..c107019 100644
--- a/tests/system/ixfr/README
+++ b/tests/system/ixfr/README
@@ -1,4 +1,7 @@
-The directories in-1 to in-4 implement the following tests:
+Introduction
+============
+The directories in-1 to in-4 implement the following tests of the IXFR-in
+capability of BIND 10.
 
 in-1: Check that BIND 10 can receive IXFR in a single UDP packet.
 in-2: Check that BIND 10 can receive IXFR via TCP.
@@ -8,3 +11,68 @@ in-4: Check that BIND 10 will request IXFR when its SOA refresh times out
 The tests are described more fully in the document:
 
 http://bind10.isc.org/wiki/IxfrSystemTests
+
+Overview
+========
+All the tests use two nameservers:
+
+* A BIND 9 nameserver acting as the IXFR server (using the nomenclature
+of RFC 1995).
+* A BIND 10 nameserver acting at the IXFR client.
+
+In general, the tests attempt to set up the server and client independently.
+Communication is established between the systems by updating their
+configurations and a notification sent to the client.  This should cause the
+client to request an IXFR from the server. (The exception is test 4, where the
+request is a result of the expiration of the SOA refresh time.)
+
+A check of zone files - or in these tests, of SOA serial number - can only
+reveal that a transfer has taken place.  To check what has happened,
+e.g. whether the transfer was via UDP or whether a TCP request took place,
+the BIND 10 log file is searched for known message IDs.
+
+The searching of the log files for message IDs is one of the reasons that,
+unlike other system tests, the IXFR set of tests is broken up into separate
+tests that require the stopping and starting of nameservers (and tidying up of
+log files) between each test.  Doing this means that only the existence of a
+particular message ID needs to be checked - there is no risk that another test
+produced it.  The other reason is that the each IXFR test requires the
+nameservers to be in a specific state at the start of the test; this is easier
+to assure if they are not updating one another as the result of configuration
+settings established in the previous test.
+
+Test Files
+==========
+
+Data Files
+----------
+(All within tests/system/ixfr.)
+
+largezone_n-X.db: These files hold the RRs for a zone for which should not
+fit within a single UDP packet.  The files are different versions of the zone
+- the N-0 version (i.e. the latest version - "N" - the "-0" is present so
+that the files have a consistent name), N-2 etc. (See the full description
+of the tests for the meaning of N-2 etc.)
+
+largezone_n-2_refresh.db: The N-2 version of the zone, but with a small SOA refresh time (for test 4)
+
+Directories
+-----------
+The tests/system/ixfr directory holds the IXFR tests.  Within that
+directory are subdirectories in-1 through in-4 for each test.  And within
+each test directory are the directories ns1 (for the BIND 9 nameserver)
+and nsx2 (for the BIND 10 nameserver).
+
+Shell Scripts
+-------------
+The IXFR tests use the same framework as the rest of the system tests,
+being based around shell scripts.  Many have a ".in" form as they require
+substitution of build variables before they can be used, and so are
+listed in configure.ac.  The files specific to the IXFR tests are:
+
+tests/system/ixfr/ixfr_init.sh.in: defines environment variables and shell
+subroutines used in the tests.  (This references system/conf.sh.in which
+defines most of them.)
+
+tests/system/ixfr/common_tests.sh.in: tests in-1 and in-2 are virtually
+identical - this holds the common code.