BIND 10 #3205: Unit-test improvement: need to use .spec defaults
BIND 10 Development
do-not-reply at isc.org
Tue Oct 22 13:26:29 UTC 2013
#3205: Unit-test improvement: need to use .spec defaults
-------------------------------------+-------------------------------------
Reporter: tomek | Owner:
Type: defect | Status: new
Priority: medium | Milestone: DHCP
Component: dhcpconf | Outstanding Tasks
Keywords: | Resolution:
Sensitive: 0 | CVSS Scoring:
Sub-Project: DHCP | Defect Severity: Low
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Description changed by tomek:
Old description:
> 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.
New description:
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#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list