Add a test for patch doc with zero patch resources

[michielbdejong]

Thanks @edwardsph for reporting this in solid-contrib/test-suite#132 (comment)

The spec says a patch doc must at least have one patch resource. It does not say what a server should do when a client violates this requirement. A 422 response sounds good, but is it wrong for a server to respond with 200 in this case?

Is there some generic statement in the spec somewhere that explains what servers should do when clients misbehave?

[edwardsph]

The think the spec does say how a server should respond to any invalid N3 patch:

Servers MUST respond with a 422 status code [RFC4918] if a patch document does not satisfy all of the above constraints.

See https://solidproject.org/ED/protocol#server-patch-n3-invalid

[michielbdejong]

Cool!
@mrvahedi68 can you write a test for this?