Fix abort condition for undelegated tests in the Basic module #1401
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
When running the full test suite (i.e. not a specific module nor test case), an evaluation of the results from the Basic module is made (specifically what is returned by Basic02) before continuing onto other Test modules. Due to an oversight in a previous refactoring, this abort condition was changed, which made all undelegated tests to never abort, even without any working name server. This PR fixes that.
Context
Release testing v2024.2
See zonemaster/zonemaster-cli#402 (comment)
Fixes zonemaster/zonemaster#1275
How to test this PR
Unit tests should pass. Running the full test suite for an undelegated test should now properly abort when no working name servers are found:
And in the normal case (working NS):