The Hurl end-to-end tests only send and check XML, while every endpoint also accepts and produces JSON. The JSON format isn't a direct translation of the XML: the system property listing, for example, is {"property": [...]} where the XML is <properties>. Only a few services pin their JSON output, in the *BackwardCompatibilityTest unit tests, and JSON-specific problems have been reported before (#20, #163).
The Hurl 8 support added in #289 brings RFC 9535 JSONPath, whose filter expressions allow JSON assertions equivalent to the existing XPath ones.
Add JSON variants of the key tests, covering both JSON request bodies and JSON responses, starting with the endpoints that have no JSON coverage in the unit tests.
The Hurl end-to-end tests only send and check XML, while every endpoint also accepts and produces JSON. The JSON format isn't a direct translation of the XML: the system property listing, for example, is
{"property": [...]}where the XML is<properties>. Only a few services pin their JSON output, in the*BackwardCompatibilityTestunit tests, and JSON-specific problems have been reported before (#20, #163).The Hurl 8 support added in #289 brings RFC 9535 JSONPath, whose filter expressions allow JSON assertions equivalent to the existing XPath ones.
Add JSON variants of the key tests, covering both JSON request bodies and JSON responses, starting with the endpoints that have no JSON coverage in the unit tests.