Update specification of Zone01 - #1028#1032
Conversation
|
We should try to have consistent format of the test case specifications. For that purpose there is a template for the specification, Template01.md. Also look at recently created or updated test case specifications such as DNSSEC18 and draft Zone09. There is also a specification of DNS query (#1000) that has been reviewed, but it requires a final approval. With that the specification can be further standardised. |
…late requirements
|
I have updated this (new) specification to meet the template's requirements. I have done what I can to detail the Test Procedure but that will surely require more work, help appreciated @matsduf . |
|
Now that I look more at Zone01 in details (specification and implementation), it appears to be greatly overlapping with this PR, especially when you consider Zone01 title name. And so I can't seem to justify to add this new test case rather than updating Zone01 instead. Wasn't the goal of Zone01 to do just what we are trying to do now? What do you think? |
I think you are right. I missed that when writing the issue. I agree it is better to update Zone01. |
I have renamed this PR, its content, and the associated issue. Thanks for the comments, I will address them when I can. |
Also look at the Objective of the current Zone01. It might have references that make sense. The more references the better. |
matsduf
left a comment
There was a problem hiding this comment.
It is easier to handle the text in general if lines are kept to 80 characters. From the template:
Limit all lines to 80 characters with the possible exception of tables such as the one in the summary section.
Purpose
This PR proposes an update to the specification of Zone01 test as described in #1028. The corresponding implementation is provided in another PR (here).
Context
Addresses #1028 and #830