-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protecting containment triples #66
base: main
Are you sure you want to change the base?
Conversation
The tests that are there now working. We can discuss whether we should have tests for |
The requirement says the server must not allow something to update its containment triples. This test focusses on invalid containment triples but should it also confirm that we can't add valid ones or change any with new valid ones? Should the test confirm that you can use PUT to add something like a title? |
This test is repetitive and could be converted to the ScenarioOutline style where the test title and payload are put into a table in the Background. |
Good point. Indeed, these tests would fail in that they modify the containment triples that aren't there. So yes, these tests aren't good. Instead, we should |
This test should also demonstrate that valid changes can be made to the container resource, then we are proving that only the containment triples are being protected. |
Here's an initial attempt at tests to protect containment triples, but it doesn't work. I'm trying to construct an array of the URLs with
* def children = [ resource1.url, resource2.url, resource3.url, container1.url ]
but it seems to take that literally, because when I run the test, I get
so, it seems it takes the variables as literals.
I have also tried
but then I get