npm supertest intercepts middleware and does not run boot scripts

[varunj90]

We are registering our middleware handler in server/middleware.json like the following:

When performing integration tests using supertest :

the code does not go through our middleware which contains the error handler because of which we get errors like

here11111111111111111111111111111111111111111111:
{ [Error: Parse Error] bytesParsed: 9, code: 'HPE_INVALID_STATUS', response: undefined }

OR
here11111111111111111111111111111111111111111111:
[TypeError: Cannot read property 'header' of undefined]

We suspect that we have a missing configuration with supertest ;
or
We might need some code that starts up in server.js that links supertest properly using loopback.

Can you advice us on getting this to work as it is a major roadblock.

Thank you !

[varunj90]

Anything that is other than code 2xx ; example in this case 500; fails with 'res' being undefined?

[varunj90]

@raymondfeng

Latest Finding: if we add the following code snippet for the unit tests, they actually pass

Reference in server.js : start function

Reference in server.js : stopServer function

Although, we shouldn't be required to start and stop a server since that's the job of supertest; but this to some extent confirms the issue of 'res' being undefined because the supertest server shuts down early? Is this a bug in supertest? Thoughts?

[mikelax]

Although, we shouldn't be required to start and stop a server since that's the job of supertest; but this to some extent confirms the issue of 'res' being undefined because the supertest server shuts down early? Is this a bug in supertest? Thoughts?

@varunj90 I actually don't think that supertest is responsible for setting up and tearing down an api server. The few examples in the README.md include express and set up a quick express server for the sake of a quick demo. supertest is a wrapper around superagent and handles making requests and evaluating responses, but not the actual server.