BIND 10 #3205: Unit-test improvement: need to use .spec defaults

[BIND 10 Development]

#3205: Unit-test improvement: need to use .spec defaults
-------------------------------------+-------------------------------------
                   Reporter:  tomek  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  DHCP
                   Priority:         |  Outstanding Tasks
  medium                             |              Keywords:
                  Component:         |             Sensitive:  0
  dhcpconf                           |           Sub-Project:  DHCP
               CVSS Scoring:         |  Estimated Difficulty:  0
            Defect Severity:  Low    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 See ticket:3191:comment:7 about the details.

 Current DHCPv4/6 unit-tests that use config files use them as is. The
 bindctl interface on the other hand, matches them against .spec files
 first and applies any default values from .spec. We do not test for that.
 Some things may work in unit-tests, but with defaults applied they may
 fail.

 Specific example: next-server with defined only global value was
 overridden on subnet scope by default value of 0.0.0.0.

-- 
Ticket URL: <http://bind10.isc.org/ticket/3205>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development