solid-contrib/solid-crud-tests

Skipped tests for PATCH-to-replace (not present)

Closed this issue · 1 comments

We don't know what the desired behaviour is for PATCH-to-replace (not present).

Since the issue of has not been settled yet at the spec level, we'll accept both behaviours for now.

See:

As soon as we know what the desired behaviour is, we'll test for that and can close this issue.

The test suite will start sending application/sparql-update-single-match as the Content-Type, and then we unskip this test.