"Should fail" examples framework - #1074
Merged
Merged
Conversation
TuThoThai
requested review from
Aurige,
TuThoThai,
albanpeignier,
atibaut,
skinkie,
tim-rivett and
ue71603
September 17, 2026 20:11
ue71603
approved these changes
Sep 18, 2026
Aurige
approved these changes
Sep 18, 2026
This was referenced Sep 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
As suggested by @Aurige, I'm moving out the new "should fail test harness" (introduced in #1032, related to #998) in a separate PR for clarity.
This PR introduces negative examples: examples that should not be considered XSD-valid.
(only 3 to get our feet wet & to separate concerns with #998/#1032).
Assertions checks have been narrowed compared to original implementation.