Cannot read property 'status' of undefined

[jakubknejzlik]

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).

[mikelax]

thanks @jakubknejzlik can you please post a small test snippet showing the problem?

[isaac-peka]

I'm also experiencing this problem when using multiple callbacks in a single route - status is undefined on the response object. I haven't had a chance to test how this behaves with single callback routes, but here's a quick example for the multiple callback issue:

function callback1(req, res, next) {
  if (!res.status) {
    throw new Error("res.status is undefined");
  } else {
    next();
  }
}

function callback2(req, res, next) {
  res.json({ success: true });
}

app.get('/test', callback1, callback2);

Then $ curl http://localhost:3000/test will return { success: true }.

The following test fails for me due to the throw above, I use Jest but this could easily be changed to use mocha:

 it("shouldn't throw an error", (done) => {
    supertest(app)
      .get('/test')
      .expect(200)
      .end((err, res) => err ? done.fail(err) : done());
 });

I'm using supertest v1.2.0 and express v4.14.0.

[jeffijoe]

In my case I was using then to end the request instead of end, and supertest adds logic to wait for the server to actually be listening for end which was not executing for then. In my before I just ensure that tests wont run until the server is listening.

It might be a good idea to add the waiting logic in a then on Test?

[Starefossen]

This is how I solved it using Promises from Supertest@2.0.0:

it('should return 404 Not Found for missing resources', function() {
  return req.get('/this/is/not/found')
    .expect(404)
    .expect(function(res) {
      assert.equal(res.body.message, 'Resource Not Found');
    });
});

[Vanuan]

Here's a traceback:

     TypeError: Cannot read property 'status' of undefined
      at Test._assertStatus (node_modules/supertest/lib/test.js:229:10)
      at Test._assertFunction (node_modules/supertest/lib/test.js:247:11)
      at Test.assert (node_modules/supertest/lib/test.js:148:18)
      at Server.assert (node_modules/supertest/lib/test.js:127:12)
      at net.js:1277:10    

[Vanuan]

Similarly,

     TypeError: Cannot read property 'header' of undefined
      at Test._assertHeader (node_modules/supertest/lib/test.js:208:19)
      at Test._assertFunction (node_modules/supertest/lib/test.js:247:11)
      at Test.assert (node_modules/supertest/lib/test.js:148:18)
      at Server.assert (node_modules/supertest/lib/test.js:127:12)
      at net.js:1277:10    

[Vanuan]

Looks like #348 is a fix

[Vanuan]

This happens when I use res.sendFile.

[santanu-biswas]

Submitted #348 almost three months back and it should take care of this bug. However, it seems that the repository is not active and nobody is accepting PRs!

[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.

[cwdcwd]

FWIW. I run into this very error when I run under node 6.9.2 (LTS) but don't see it when I switch to 4.0.0. Is this an ES6 related issue?

     TypeError: Cannot read property 'status' of undefined
      at Test._assertStatus (node_modules/supertest/lib/test.js:263:10)
      at Test._assertFunction (node_modules/supertest/lib/test.js:281:11)
      at Test.assert (node_modules/supertest/lib/test.js:171:18)
      at Server.assert (node_modules/supertest/lib/test.js:131:12)
      at emitCloseNT (net.js:1555:8)
      at _combinedTickCallback (internal/process/next_tick.js:71:11)
      at process._tickDomainCallback (internal/process/next_tick.js:122:9)

[cwdcwd]

tracing through my particular issue, res is undefined and I'm seeing and HPE_UNEXPECTED_CONTENT_LENGTH error. That led me to this which seems to imply it's an issue w/ request & node.js versioning.

[cwdcwd]

upgrading all my dependencies, including request seems to have resolved this for me. here's a snippet of all my deps:

{
        "async": "^2.1.4",
        "aws-sdk": "2.7.13",
        "bluebird": "3.4.6",
        "body-parser": "^1.15.2",
        "config": "^1.24.0",
        "express": "^4.14.0",
        "express-http-proxy": "^0.10.1",
        "http-auth": "^3.1.1",
        "kue": "^0.11.5",
        "lodash": "4.17.2",
        "morgan": "^1.7.0",
        "request": "^2.79.0",
        "throng": "^4.0.0",
        "underscore": "^1.8.3",
        "url": "^0.11.0",
        "winston": "^2.3.0"
    }

[turakvlad]

I have the same issue with node 7.2.1:

     TypeError: Cannot read property 'status' of undefined
      at Test._assertStatus (node_modules/supertest/lib/test.js:263:10)
      at Test._assertFunction (node_modules/supertest/lib/test.js:281:11)
      at Test.assert (node_modules/supertest/lib/test.js:171:18)
      at assert (node_modules/supertest/lib/test.js:131:12)
      at node_modules/supertest/lib/test.js:128:5
      at Test.Request.callback (node_modules/superagent/lib/node/index.js:615:12)
      at ClientRequest.<anonymous> (node_modules/superagent/lib/node/index.js:567:10)
      at Socket.socketErrorListener (_http_client.js:309:9)
      at onwriteError (_stream_writable.js:346:10)
      at onwrite (_stream_writable.js:364:5)
      at WritableState.onwrite (_stream_writable.js:90:5)
      at fireErrorCallbacks (net.js:471:13)
      at Socket._destroy (net.js:512:3)
      at WriteWrap.afterWrite (net.js:806:10)

It fails sometimes. About 1 to 10 times. My test looks pretty straight forward:

it('should fail because the token has already been used', function (done) {
            request(server)
                .post(`${apiPath}/${token}/actions/create`)
                .attach('upload', filePath)
                .expect(400)
                .end((err, res) => {
                    if (err) return done(err);
                    expect(res.body.success).to.be.false;
                    done();
                })
        });

My deps:

  "dependencies": {
    "cron": "^1.1.1",
    "debug": "~2.2.0",
    "dotenv": "^2.0.0",
    "express": "^4.14.0",
    "extract-zip": "^1.5.0",
    "formidable": "^1.0.17",
    "jsonfile": "^2.4.0",
    "mysql": "^2.11.1",
    "promise": "^7.1.1",
    "request": "^2.79.0",
    "shelljs": "^0.7.5"
  },
  "devDependencies": {
    "babel-cli": "^6.18.0",
    "babel-preset-es2015": "^6.18.0",
    "babel-preset-stage-2": "^6.18.0",
    "babel-register": "^6.18.0",
    "chai": "^3.5.0",
    "mocha": "^3.2.0",
    "supertest": "^2.0.1"
  }