Any way to make JSON body assertion ignore formatting?

[micka190]

I'm trying to assert that a response's body has a specific JSON structure:

{
    "success": true,
    "payload": null,
    "errors": {
        "all": []
    }
}

However, the API I'm testing against minifies the JSON output, so it becomes:

{"success": true,"payload": null,"errors": {"all": []}}

Using the following Hurl body assertion fails, because the output isn't pretty-formatted:

HTTP 200
{
  "success": true,
  "payload": null,
  "errors": {
    "all": []
  }
}

It's not too bad when I have a small response, but some of these can get quite large, and placing everything on a single line makes them pretty-much impossible to read properly.

Is there a way to make the assertion ignore the formatting difference? Or do I need to work around it by dropping the JSON body assertion and just using jsonpath everywhere instead?

[jcamiel]

Hi @micka190

Thanks for the feedback. Effectively, the current JSON body assertion is whitespace sensitive and we want to change this. In a future release:

GET https://foo.com
HTTP 200
{
  "success": true,
  "payload": null,
  "errors": {
    "all": []
  }
}

Will do a "semantic" assertion (whitespace insentive), that we've to specify, while:

GET https://foo.com
HTTP 200
```json
HTTP 200
{
  "success": true,
  "payload": null,
  "errors": {
    "all": []
  }
}
```

Will do an exact match assertion.

There're similar issue and we want to address them #270 #272
Another possibility (still not implemented) is to add support for JSON schema #543

[micka190]

Thanks for clarification! I'll keep using jsonpaths in the meantime.