Add unit tests to validate / invalidate examples based on SHACL#68
Closed
mgrub wants to merge 2 commits into
Closed
Add unit tests to validate / invalidate examples based on SHACL#68mgrub wants to merge 2 commits into
mgrub wants to merge 2 commits into
Conversation
Merged
mgrub
added a commit
that referenced
this pull request
May 27, 2026
- merge multiple tests into one python file - remove duplicate reasoner.py (and keep equivalent test_reasoner.py) - rename unit_shacl.ttl to unit_definition_shacl.ttl - redefine testing of resbod - add additional tests for prefixed units as proposed in #68
Collaborator
Author
|
The core idea of this PR was implemented via #87 . |
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
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.
This (draft) pull request adds the possibility to verify valid / falsify invalid individuals against provided SHACL constraints as part of the CI pipeline.
As of now, only constraints with regard to "si:PrefixedUnits" are provided, but this can be extended easily (without changes to the Python code).
The process is not fully automated and (as of now) the developer is required to check, if really every invalid example is actually invalidated. I will think about a way to automate this.