Better error reporting

Two things, really.

One: assertions are not thrown first-come first-served. If I have:

return request(app)
    .post('/api/sites')
    .send(site)
    .expect(201)
    .expect('Location', new RegExp('/api/site/\\d+'))
    .end()

And my app returns a 400 error, it fails on the ‘Location’ header, even though the .expect(201) method is called first. If I remove the .expect('Location', ...) method call, it does fail on 201 !== 400.

Truth be told, I’d rather have the HTTP status code checked before any headers, since it’s a “higher level”, but manual ordering in the source gives more control.

Secondly, if a body is available, it would be nice to report the body contents, at least optionally or on error conditions, since that can provide details as to why the request failed.

[kjarmicki]

I was having the same issue with insufficient debugging information on failing status assertions, so I made a minimal plugin to capture and enhance errors: https://github.com/kjarmicki/supertest-capture-error It should give you enough flexibility to decorate assertion errors with valuable info.

[maldimirov]

+1 for printing the body on status code expectation fail. Right now I use supertest only for status and header assertions and Jest for body checking. The only way to check why a request has failed is to try/catch/log the script being tested.