Cannot read property 'status' of undefined

When sending test request with expected status code and getting response with invalid content type (eg. header says application/json, but server sends xml/html), the Test.prototype._assertStatus fails while getting status from res (which is undefined).

[danday74]

I got this error when testing over a secure connection. I fixed it by adding NODE_TLS_REJECT_UNAUTHORIZED=0 as an env var on the test run.

For those wondering why this happens, it can happen because ‘127.0.0.1’ is not listed as a valid IP in your certificate. The underlying error is … Hostname/IP doesn’t match certificate’s altnames: "IP: 127.0.0.1 is not in the cert’s list: " However, you will not see this error message - Just the spurious and much disliked …

Cannot read property ‘status’ of undefined

Hope this helps someone. God bless.

[01binary]

Just got this error, and my problem is that I forgot the slash in get path: supertest(server).get('favicon.ico') gets me…

TypeError: Cannot read property 'status' of undefined
at Test.Object.<anonymous>.Test._assertStatus (node_modules/supertest/lib/test.js:268:10)
      at Test.Object.<anonymous>.Test._assertFunction (node_modules/supertest/lib/test.js:286:11)
      at Test.Object.<anonymous>.Test.assert (node_modules/supertest/lib/test.js:175:18)
      at Server.assert (node_modules/supertest/lib/test.js:132:12)

putting the slash in, supertest(server).get('/favicon.ico') …the test works as expected.

I traced the issue down to logic that applies assertions. It’s supposed to early-exit with an error if there was an error, but something causes it to run the assertions anyway and it fails because response is undefined when there’s an error:

callback that performs assertions gets resError { Error: connect ECONNREFUSED 127.0.0.1:80
          at Object._errnoException (util.js:1041:11)
          at _exceptionWithHostPort (util.js:1064:20)
          at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1153:14)
        code: 'ECONNREFUSED',
        errno: 'ECONNREFUSED',
        syscall: 'connect',
        address: '127.0.0.1',
        port: 80,
        response: undefined } res undefined

Maybe it fails because the un-intended effect of forgetting the slash means that it will try to connect to “http://favicon.ico” which isn’t a server?

Either way it needs some logic hardened in Test.assert (or whatever runs through the array of assertions and applies them) and a friendly error message saying it Couldn't connect to http://favicon.ico:80 to run the tests instead of throwing some IP number out - there is no way to know what that means without reading the whole library.