Skip to content

Add test scenario specification for Zone11#1417

Merged
marc-vanderwal merged 4 commits into
zonemaster:developfrom
marc-vanderwal:feature/zone11-test-scenario-specification
Nov 14, 2025
Merged

Add test scenario specification for Zone11#1417
marc-vanderwal merged 4 commits into
zonemaster:developfrom
marc-vanderwal:feature/zone11-test-scenario-specification

Conversation

@marc-vanderwal

@marc-vanderwal marc-vanderwal commented Aug 7, 2025

Copy link
Copy Markdown
Contributor

Purpose

This PR adds a test scenario specification for Zone11 that matches the test case specification as worded in #1415.

Of note here are the scenarios that perform tests on three different root zones. They will require three changes to the root hints during unit testing.

Context

See #1256 (issue about Zone11).

Depends on #1415 (Zone11 test case specification update).

Changes

  • Add test scenario specification for Zone11.

How to test this PR

Review.

@marc-vanderwal marc-vanderwal added this to the v2025.2 milestone Aug 7, 2025
@marc-vanderwal marc-vanderwal added the A-TestCase Area: Test case specification or implementation of test case label Aug 7, 2025
@matsduf matsduf added RC-Features Release category: Features. RC-None Release category: Not to be included in Changes file. and removed RC-Features Release category: Features. labels Aug 10, 2025

@matsduf matsduf left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test zones are not included.

Comment thread docs/public/specifications/test-zones/Zone-TP/zone11.md Outdated
Comment thread docs/public/specifications/test-zones/Zone-TP/zone11.md Outdated
Comment thread docs/public/specifications/test-zones/Zone-TP/zone11.md Outdated
Comment thread docs/public/specifications/test-zones/Zone-TP/zone11.md Outdated
@marc-vanderwal

Copy link
Copy Markdown
Contributor Author

The test zones are not included.

Yes, they’re coming, but I wanted some early feedback on the outline of the test scenarios before completing them.

@marc-vanderwal marc-vanderwal force-pushed the feature/zone11-test-scenario-specification branch from 34a9b4a to b3a3162 Compare August 13, 2025 13:52
@marc-vanderwal marc-vanderwal marked this pull request as draft August 13, 2025 13:53
@matsduf matsduf dismissed their stale review October 20, 2025 13:56

Looks fine now. Waiting for the configuration of the test case to be completed.

@marc-vanderwal marc-vanderwal force-pushed the feature/zone11-test-scenario-specification branch from b3a3162 to 0f3b089 Compare November 5, 2025 07:05
@marc-vanderwal

Copy link
Copy Markdown
Contributor Author

Test zones complete (and tested manually); the only thing I’m missing now is the test-zones-output.md file. @tgreenx, this should be enough to help you with testing the updated implementation for Zone11.

Comment thread test-zone-data/Zone-TP/zone11/zone11.xa.zone Outdated
Comment thread docs/public/specifications/test-zones/Zone-TP/zone11.md Outdated
@marc-vanderwal marc-vanderwal force-pushed the feature/zone11-test-scenario-specification branch from 0f3b089 to 53ecb49 Compare November 5, 2025 12:03
@marc-vanderwal marc-vanderwal marked this pull request as ready for review November 5, 2025 12:09
@marc-vanderwal

Copy link
Copy Markdown
Contributor Author

Everything complete. I noticed however a mistake in the arpa zone apex’s NS record set. I had to fix it here, or else I was unable to test the scenarios that live in {SCENARIO}.zone11.arpa (not xa!).

Comment on lines +48 to +51
$ORIGIN zone11.arpa.
@ NS ns1.zone11.xa.
@ NS ns2.zone11.xa.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is one way to do it. I have moved to creating test case dedicated root, xa and other zones instead to have as few shared files as possible to cut down the risk of conflicts

@matsduf matsduf left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine. The final test is when used as unit tests.

Comment on lines +21 to +23
;; Local Variables:
;; mode: dns
;; End:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this for Emacs?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is to switch to dns-mode instead of fundamental-mode when visiting the file in Emacs.

@tgreenx tgreenx added the A-Documentation Area: Documentation only. label Nov 6, 2025

@tgreenx tgreenx left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few minor comments otherwise LGTM

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(File to be updated before merging)

Comment thread docs/public/specifications/test-zones/Zone-TP/zone11.md Outdated
Comment thread docs/public/specifications/test-zones/Zone-TP/zone11.md Outdated
Comment thread docs/public/specifications/test-zones/Zone-TP/zone11.md Outdated
Comment thread docs/public/specifications/test-zones/Zone-TP/zone11.md Outdated
Comment thread docs/public/specifications/test-zones/Zone-TP/zone11.md Outdated
Comment thread docs/public/specifications/test-zones/Zone-TP/zone11.md Outdated
Comment thread docs/public/specifications/test-zones/Zone-TP/zone11.md Outdated
Comment thread docs/public/specifications/test-zones/Zone-TP/zone11.md Outdated
Comment thread test-zone-data/Zone-TP/zone11/zone11.xa.zone Outdated
The overhaul of the test specification for Zone11 (see zonemaster#1415) is a good
opportunity to add some test scenarios for that same test case.

Of note here are the scenarios that perform tests on three different
root zones. They will require three changes to the root hints during
unit testing.
Comment thread test-zone-data/Zone-TP/zone11/zone11.xa.zone Outdated
Add the test zones and the CoreDNS configuration files implementing the
test scenario specification for Zone11.
The parent (root zone) delegates arpa. to ns1. and ns2., but the NS
records at the apex of the arpa. zone listed different name servers:
ns1.xa and ns2.xa. This inconsistency caused some odd errors when trying
to run zonemaster-cli on those test zones, while preparing the
test-zones-output.md.

This might be the sign of a bug somewhere in Basic02, which should
warrant further investigation.
Add the output for test scenarios.
@marc-vanderwal marc-vanderwal force-pushed the feature/zone11-test-scenario-specification branch from 53ecb49 to c355f40 Compare November 6, 2025 15:19
@tgreenx tgreenx requested a review from matsduf November 6, 2025 16:37

@matsduf matsduf left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine.

@matsduf

matsduf commented Nov 13, 2025

Copy link
Copy Markdown
Contributor

@marc-vanderwal, please merge.

@marc-vanderwal marc-vanderwal merged commit 9fc02ee into zonemaster:develop Nov 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-Documentation Area: Documentation only. A-TestCase Area: Test case specification or implementation of test case RC-None Release category: Not to be included in Changes file.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants