BIND 10 #174: Loadzone: Make a collection of zone files to test loadzone

[BIND 10 Development]

#174: Loadzone: Make a collection of zone files to test loadzone
------------------------+---------------------------------------------------
 Reporter:  zhanglikun  |        Owner:  zhanglikun                 
     Type:  task        |       Status:  new                        
 Priority:  major       |    Milestone:  04. 2nd Incremental Release
Component:  loadzone    |   Resolution:                             
 Keywords:              |    Sensitive:  0                          
------------------------+---------------------------------------------------

Comment(by jreed):

 tingting-loadzone as of revision 1901 is a great start.
 A few suggestions:

 - I am not sure if all versions of dig will give the same output (maybe
 formatted different in some case).

 - Assumes server is running. Could also use a tool like sqlite to export
 data from the db and use that to compare.

 - use @builddir@/src/bin/loadzone/b10-loadzone instead of just
 b10-loadzone in path.

 - use the b10-loadzone -d to choose an testing sqlite db file. Remove the
 db file before each use unless you expect to test using a pre-existing db
 file.

 - use separate expected output files for each zone file tested that way
 failures can be identified easier/quicker for a specific failure

 - don't include the generated file in svn (that will be overwritten) like
 error.out.

 - also integrate with make check -- I will think of way to do this cleanly
 and correctly.

 Thanks for your work on this! It is useful.

 I am sure others, including myself, will add more tests to this.

 Also maybe later cucumber will be used. Or at least cucumber could be
 trained to use the same test data.

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