From: Kees Monshouwer Date: Fri, 13 Sep 2013 20:06:37 +0000 (+0200) Subject: format test descriptions X-Git-Tag: rec-3.6.0-rc1~442^2~2 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=dd9e11ea82c47990df80c925e508506dd3db76a2;p=pdns format test descriptions --- diff --git a/regression-tests/0dyndns-prereq-all/description b/regression-tests/0dyndns-prereq-all/description index b10d1f2b7..a60a07d19 100644 --- a/regression-tests/0dyndns-prereq-all/description +++ b/regression-tests/0dyndns-prereq-all/description @@ -1,2 +1,3 @@ -This test checks section 3.2.1 and 3.2.3 of RFC2136, which is the prerequisite section. -This test also checks to see what happens when a backend does NOT support RFC2136. +This test checks section 3.2.1 and 3.2.3 of RFC2136, which is the prerequisite +section. This test also checks to see what happens when a backend does NOT +support RFC2136. diff --git a/regression-tests/0dyndns-prereq-nxrrset-full/description b/regression-tests/0dyndns-prereq-nxrrset-full/description index 9bcbd5c3e..8b3c8fd21 100644 --- a/regression-tests/0dyndns-prereq-nxrrset-full/description +++ b/regression-tests/0dyndns-prereq-nxrrset-full/description @@ -1 +1,2 @@ -This test checks the specific case mentioned in RFC2136 3.2.3, where an RRSet is needed, and not the specific record. +This test checks the specific case mentioned in RFC2136 3.2.3, where an RRSet is +needed, and not the specific record. diff --git a/regression-tests/1dyndns-big-package/description b/regression-tests/1dyndns-big-package/description index 006577e52..c8994d7ab 100644 --- a/regression-tests/1dyndns-big-package/description +++ b/regression-tests/1dyndns-big-package/description @@ -1 +1,2 @@ -PowerDNS truncates incoming UDP packages. This might have effect on RFC2136 operation as packages might be very big. +PowerDNS truncates incoming UDP packages. This might have effect on RFC2136 +operation as packages might be very big. diff --git a/regression-tests/1dyndns-update-add-delete-casesensative/description b/regression-tests/1dyndns-update-add-delete-casesensative/description index a8e53f4fb..af35fda3e 100644 --- a/regression-tests/1dyndns-update-add-delete-casesensative/description +++ b/regression-tests/1dyndns-update-add-delete-casesensative/description @@ -1,2 +1,4 @@ -This test performs a simple add and delete of a A and TXT record. This is typically with ISC's DHCPD does. -The interesting thing is the case-sensativity, as hosts can have capital letters in them (it's how you configure the dhcpd's client machine). +This test performs a simple add and delete of a A and TXT record. This is +typically with ISC's DHCPD does. The interesting thing is the case-sensativity, +as hosts can have capital letters in them (it's how you configure the dhcpd's +client machine). diff --git a/regression-tests/1dyndns-update-add-delete-cname/description b/regression-tests/1dyndns-update-add-delete-cname/description index 58fe8e142..38191946c 100644 --- a/regression-tests/1dyndns-update-add-delete-cname/description +++ b/regression-tests/1dyndns-update-add-delete-cname/description @@ -1,2 +1,3 @@ -A test to see if RFC2136 add and delete record works properly on a cname record. This is important because CNAME's have a special function -when they are replaced. This test aims to check add/delete of the cname. +A test to see if RFC2136 add and delete record works properly on a cname record. +This is important because CNAME's have a special function when they are +replaced. This test aims to check add/delete of the cname. diff --git a/regression-tests/1dyndns-update-add-soa/description b/regression-tests/1dyndns-update-add-soa/description index c133334de..037507ba2 100644 --- a/regression-tests/1dyndns-update-add-soa/description +++ b/regression-tests/1dyndns-update-add-soa/description @@ -1 +1,2 @@ -This test tries to add SOA records in different ways which should all fail. Soa's are only updated (see 2dyndns-update-replace-soa) +This test tries to add SOA records in different ways which should all fail. +Soa's are only updated (see 2dyndns-update-replace-soa) diff --git a/regression-tests/1dyndns-update-deep-add-delete/description b/regression-tests/1dyndns-update-deep-add-delete/description index 0ebef9394..d3d78000b 100644 --- a/regression-tests/1dyndns-update-deep-add-delete/description +++ b/regression-tests/1dyndns-update-deep-add-delete/description @@ -1,2 +1,3 @@ -This test performs a simple add and delete of an A-record on a very deep level, which should cause ENT's to be inserted. -This test also validates if the cache is cleaned properly and NSEC(3) records are returned correctly. +This test performs a simple add and delete of an A-record on a very deep level, +which should cause ENT's to be inserted. This test also validates if the cache +is cleaned properly and NSEC(3) records are returned correctly. diff --git a/regression-tests/1dyndns-update-deep-delegate/description b/regression-tests/1dyndns-update-deep-delegate/description index 99787688f..aa06ec440 100644 --- a/regression-tests/1dyndns-update-deep-delegate/description +++ b/regression-tests/1dyndns-update-deep-delegate/description @@ -1 +1,2 @@ -This test adds a delegate and a delegate at a deeper level. It validates that ordername and auth are set correctly and no ENT's are inserted. \ No newline at end of file +This test adds a delegate and a delegate at a deeper level. It validates that +ordername and auth are set correctly and no ENT's are inserted. diff --git a/regression-tests/1dyndns-update-delegate-in-between/description b/regression-tests/1dyndns-update-delegate-in-between/description index aa2a022c0..d3ca0904f 100644 --- a/regression-tests/1dyndns-update-delegate-in-between/description +++ b/regression-tests/1dyndns-update-delegate-in-between/description @@ -1,2 +1,3 @@ -This tests adds a delegate between two (existing) records. The test validates that we set our ordername correctly. -It also validates that our cache is correctly purged (when we are selective about it). \ No newline at end of file +This tests adds a delegate between two (existing) records. The test validates +that we set our ordername correctly. It also validates that our cache is +correctly purged (when we are selective about it). diff --git a/regression-tests/1dyndns-update-delegate/description b/regression-tests/1dyndns-update-delegate/description index c415568d7..28a113d84 100644 --- a/regression-tests/1dyndns-update-delegate/description +++ b/regression-tests/1dyndns-update-delegate/description @@ -1,3 +1,5 @@ -For DNSSEC, PowerDNS uses the Auth and Ordername fields in the database. This tests adds an (delegate) NS and A record -to the test.dyndns zone, it also deletes these records. The test is rather big because it should cover -all the scenario's. This thus validates the correction of these records, known as rectify-zone. +For DNSSEC, PowerDNS uses the Auth and Ordername fields in the database. This +tests adds an (delegate) NS and A record to the test.dyndns zone, it also +deletes these records. The test is rather big because it should cover all the +scenario's. This thus validates the correction of these records, known as +rectify-zone. diff --git a/regression-tests/1dyndns-update-delete-add-host/description b/regression-tests/1dyndns-update-delete-add-host/description index 37abe2caa..f2bad4de4 100644 --- a/regression-tests/1dyndns-update-delete-add-host/description +++ b/regression-tests/1dyndns-update-delete-add-host/description @@ -1 +1,2 @@ -This test deletes a record and add's it again. Another record with the same name exists, this test check if we only delete the correct record. +This test deletes a record and add's it again. Another record with the same name +exists, this test check if we only delete the correct record. diff --git a/regression-tests/1dyndns-update-delete-multi-add-host/description b/regression-tests/1dyndns-update-delete-multi-add-host/description index 32448ba27..8bfc324ce 100644 --- a/regression-tests/1dyndns-update-delete-multi-add-host/description +++ b/regression-tests/1dyndns-update-delete-multi-add-host/description @@ -1,2 +1,2 @@ -This test performs a delete without a record type (which removes all the items with that name). -It then adds the records again. Also contains an 'add' to the TXT +This test performs a delete without a record type (which removes all the items +with that name). It then adds the records again. Also contains an 'add' to the TXT diff --git a/regression-tests/1dyndns-update-delete-mx-prio/description b/regression-tests/1dyndns-update-delete-mx-prio/description index 5288ed58e..4c5fd4367 100644 --- a/regression-tests/1dyndns-update-delete-mx-prio/description +++ b/regression-tests/1dyndns-update-delete-mx-prio/description @@ -1,2 +1,4 @@ -This test checks to see if deleting a MX record with a specific Priority works correctly. This is -interesting because the gsql-backends store priority in a seperate field, where other backends probably store it together with the content (or RDATA). +This test checks to see if deleting a MX record with a specific Priority works +correctly. This is interesting because the gsql-backends store priority in a +seperate field, where other backends probably store it together with the content +(or RDATA). diff --git a/regression-tests/1dyndns-update-delete-ns/description b/regression-tests/1dyndns-update-delete-ns/description index e4847ed8a..1a72d48da 100644 --- a/regression-tests/1dyndns-update-delete-ns/description +++ b/regression-tests/1dyndns-update-delete-ns/description @@ -1 +1,2 @@ -This test checks if we delete NS records properly from the zone apex. There must always remain 1 NS record at the zone apex. +This test checks if we delete NS records properly from the zone apex. There must +always remain 1 NS record at the zone apex. diff --git a/regression-tests/1dyndns-update-delete-parent-delegate/description b/regression-tests/1dyndns-update-delete-parent-delegate/description index 6e3cfc6dd..06fa338d6 100644 --- a/regression-tests/1dyndns-update-delete-parent-delegate/description +++ b/regression-tests/1dyndns-update-delete-parent-delegate/description @@ -1 +1 @@ -This test adds 2 delegates below each other and deletes the top delegate. \ No newline at end of file +This test adds 2 delegates below each other and deletes the top delegate. diff --git a/regression-tests/1dyndns-update-in-between/description b/regression-tests/1dyndns-update-in-between/description index da3478a61..52a6134c1 100644 --- a/regression-tests/1dyndns-update-in-between/description +++ b/regression-tests/1dyndns-update-in-between/description @@ -1,2 +1,3 @@ -This test checks if we add a record correctly in between two other records. This requires us to correct ENT records. -The test is also focussed on checking if we purge our cache correctly. \ No newline at end of file +This test checks if we add a record correctly in between two other records. +This requires us to correct ENT records. The test is also focussed on checking +if we purge our cache correctly. diff --git a/regression-tests/1dyndns-update-nsec3params/description b/regression-tests/1dyndns-update-nsec3params/description index 702373612..79ae326ad 100644 --- a/regression-tests/1dyndns-update-nsec3params/description +++ b/regression-tests/1dyndns-update-nsec3params/description @@ -1,4 +1,6 @@ -We allow to add/remove the NSEC3PARAM record, this test confirms that everything is working correctly. -The test operates a bit different when in NSEC mode, as we don't add a NSEC3PARAM at the end. -In NSEC3-NARROW mode, we do add NSEC3PARAM's at the end, but these are then in non-narrow mode as we cannot -specify narrow mode in the NSEC3PARAM and the delete of the NSEC3PARAM also removed the narrow flag. +We allow to add/remove the NSEC3PARAM record, this test confirms that everything +is working correctly. The test operates a bit different when in NSEC mode, as we +don't add a NSEC3PARAM at the end. In NSEC3-NARROW mode, we do add NSEC3PARAM's +at the end, but these are then in non-narrow mode as we cannot specify narrow +mode in the NSEC3PARAM and the delete of the NSEC3PARAM also removed the narrow +flag. diff --git a/regression-tests/1dyndns-update-replace-cname/description b/regression-tests/1dyndns-update-replace-cname/description index d559fa35a..5456d4b87 100644 --- a/regression-tests/1dyndns-update-replace-cname/description +++ b/regression-tests/1dyndns-update-replace-cname/description @@ -1 +1 @@ -A test for RFC2136 which checks section 3.4.2.2 - Replacing CNAME record. \ No newline at end of file +A test for RFC2136 which checks section 3.4.2.2 - Replacing CNAME record. diff --git a/regression-tests/1dyndns-update-replace-mx/description b/regression-tests/1dyndns-update-replace-mx/description index 079a41f27..c121c2bd3 100644 --- a/regression-tests/1dyndns-update-replace-mx/description +++ b/regression-tests/1dyndns-update-replace-mx/description @@ -1,2 +1,3 @@ -A test for RFC2136 which checks section 3.4.2.2 - Replacing a record. -In this test, we specifically use MX record, to see if the TTL changes of the MX record with the correct priority. \ No newline at end of file +A test for RFC2136 which checks section 3.4.2.2 - Replacing a record. In this +test, we specifically use MX record, to see if the TTL changes of the MX record +with the correct priority. diff --git a/regression-tests/1dyndns-update-srv/description b/regression-tests/1dyndns-update-srv/description index 40eaf5a03..f5c4b87fd 100644 --- a/regression-tests/1dyndns-update-srv/description +++ b/regression-tests/1dyndns-update-srv/description @@ -1,2 +1,2 @@ -This test checks to see if SRV records are parsed/handled correctly when adding/updating/deleting -via RFC2136. +This test checks to see if SRV records are parsed/handled correctly when +adding/updating/deleting via RFC2136. diff --git a/regression-tests/1dyndns-update-update-ttl/description b/regression-tests/1dyndns-update-update-ttl/description index 31ce46d75..fd18319e4 100644 --- a/regression-tests/1dyndns-update-update-ttl/description +++ b/regression-tests/1dyndns-update-update-ttl/description @@ -1 +1,2 @@ -A test for RFC2136 which checks section 3.4.2.2 - Update the TTL, which occurs if the record + content is the same. +A test for RFC2136 which checks section 3.4.2.2 - Update the TTL, which occurs +if the record + content is the same. diff --git a/regression-tests/2dyndns-update-replace-soa/description b/regression-tests/2dyndns-update-replace-soa/description index b6a9ab6cd..5cbce2f41 100644 --- a/regression-tests/2dyndns-update-replace-soa/description +++ b/regression-tests/2dyndns-update-replace-soa/description @@ -1,4 +1,4 @@ -A test for RFC2136 which checks section 3.4.2.2 - Replacing a SOA record. -This is special because we can 'set' the soa serial. -This test also does not use the hidesoaserial option because we want to compare that serial. It's also the reason why the test is run only once. - +A test for RFC2136 which checks section 3.4.2.2 - Replacing a SOA record. This +is special because we can 'set' the soa serial. This test also does not use the +hidesoaserial option because we want to compare that serial. It's also the +reason why the test is run only once. diff --git a/regression-tests/5dyndns-restore-zone/description b/regression-tests/5dyndns-restore-zone/description index 80799267f..b7ff43830 100644 --- a/regression-tests/5dyndns-restore-zone/description +++ b/regression-tests/5dyndns-restore-zone/description @@ -1 +1 @@ -Restore SOA resial to it's original value \ No newline at end of file +Restore SOA resial to it's original value.