BIND 10 #606: See which of BIND 9 tests can be re-used or re-implemented for BIND 10

[BIND 10 Development]

#606: See which of BIND 9 tests can be re-used or re-implemented for BIND 10
-------------------------------------+-------------------------------------
                 Reporter:  stephen  |                Owner:  jinmei
                     Type:  task     |               Status:  accepted
                 Priority:  major    |            Milestone:  A-Team-
                Component:           |  Sprint-20110309
  b10-auth                           |           Resolution:
                 Keywords:           |            Sensitive:  0
Estimated Number of Hours:  3.0      |  Add Hours to Ticket:  0
                Billable?:  1        |          Total Hours:  0
                Internal?:  0        |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 branch trac606 is ready for review.

 Based on my moderate level of look at BIND 9's system tests, I think
 we can reuse (at least some part) the following test suites:
 - dnssec (some of it)
 - glue
 - masterfile (maybe some of it)
 - notify (this seems to be difficult though)
 - xfer (some of it)
 - resolver (probably some of it)

 These tests can be found in bind9/bin/tests/system.

 It also seemed to me that the main framework of the system test
 (start/stop the servers, etc) can be easily reused.

 So, in this branch, I did the following:
 - port the general framework
 - add some small modifications to BIND10 programs so that they can
   work under the framework
 - as an initial step of porting actual tests, port the "glue" test

 The entire diff may look a bit large, but a large part of is a copy of
 the original test code in BIND 9, which can generally be ignored.
 These changes are: 53b5297 to ddd7b7c, and 5851a6c.

 Adjustments to the existing framework are: 56df4f9 to edfcbca, and
 19f9f1.

 Other changes are modifications to BIND 10 programs.  Important
 features are:
 - a9211d7: added --pid-file to BoB so that we can stop it from the test
 framework
 - various changes to specify the location of config/temporary files so
 that the can be located under a test directory

 For general usage of the test framework, see the README file under
 tests/system.

 My plan is to get this reviewed and merged, and then add other
 possible tests on top it.

 Finally, this is the proposed changelog entry (I thought it's a
 visible feature, but I'm also okay with skipping it if it looks too
 minor in terms of user experience):

 {{{
   185.? [func]          jinmei
         Imported system test framework of BIND 9.  It can be run by
         'make systest' at the top source directory.  Notes: currently it
         doesn't work when built in a separate tree.  It also requires
         perl, an inherited dependency from the original framework.
         Also, mainly for the purpose of tests, a new option "--pid-file"
         was added to BoB, with which the boss process will dump its PID
         to the specified file.
         (Trac #606, git TBD)
 }}}

-- 
Ticket URL: <https://bind10.isc.org/ticket/606#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development