Run JSON schema validation on output of test requests #514
Description
Currently, JsonSchemaTest runs on the example requests generated/provided as part of documentation (exampleApplicationServiceRequests). However, this isn't exhaustive, as there is only one example per request (at the moment, at least).
There is a whole lot more JSON output as part of OutputXXXServiceTestRequests, used as input for BackwardsCompatibilityTest. And, it's more trivial to add coverage (just add more test cases to XXXServiceTest). Should the JsonSchemaTest run on this output instead (or in addition?)
Related: adding a test to verify full coverage (#404)