Fix GSP POST - existing graph and GET of POST - existing graph test mixup/omission
#253
Conversation
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
1 participant
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.
Fix the description of the tests
POST - existing graphandGET of POST - existing graphin the manifest.POST - existing graphhad no comment describing the test case.GET of POST - existing graphcontained the test case forPOST - existing graph.The specifications from https://www.w3.org/2009/sparql/docs/tests/data-sparql11/http-rdf-update/, but are also what I'd expect from the test names. As far as I can tell both tests have been approved in 2012, but I don't know why they got lost/mixed up.