BIND 10 #1460: Define system-level tests for DDNS
BIND 10 Development
do-not-reply at isc.org
Wed May 30 19:39:20 UTC 2012
#1460: Define system-level tests for DDNS
-------------------------------------+-------------------------------------
Reporter: jelte | Owner: UnAssigned
Type: task | Status: reviewing
Priority: | Milestone:
medium | Sprint-20120612
Component: DDNS | Resolution:
Keywords: | Sensitive: 0
Defect Severity: N/A | Sub-Project: DNS
Feature Depending on Ticket: DDNS | Estimated Difficulty: 5
Add Hours to Ticket: 0 | Total Hours: 6
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by jelte):
* owner: jelte => UnAssigned
* status: assigned => reviewing
* totalhours: 0 => 6
Comment:
Okay, I've written up a number of system tests. I split them up in BIND 10
specific tests (i.e. starting the module, and ACL checks), and a number of
'general' RFC-compliance tests.
The latter are not complete; I did not write up full tests for every
possible change to the zone, but zone section, prerequisite section, and
prescan *should* be pretty much complete, unless I've missed any
scenarios.
I am willing to do the adds/deletes and all their special cases at some
point if we think it is worth it, but these things are also tested in the
unit tests. Because of that, perhaps, if we are short on time, we may only
want to test the inter-process parts (i.e. the bind10-specific tests), and
the TCP test and the IXFR test (which perhaps should be considered
b10-specific too). But for now, I've left them out before I'm spending
more than a full day on just this document :)
The tests are written up at [wiki:DDNSSystemTests], which is mentioned at
RfcCompliance (as we finish the components, we need to update that table
there, btw)
--
Ticket URL: <http://bind10.isc.org/ticket/1460#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list