Jest runs test suites in parallel by default. However, the machine that the tests are running on only has a single port 3000 (or port 4000, etc.) This means that if you tell your app to listen on a port, and then start multiple concurrent processes, there will be a port collision and Jest will … Read more
I still haven’t found a perfect solution, but for the moment I went for this workaround : jest –config ./test/jest-e2e.json –forceExit The –forceExit option kill the openHandles somehow and unlock everything. Yet, I’m still looking for the “proper way” of handling that issue.
Alternatively, this should work too: res.body.should.have.property(“name”, “new_org”); Also, just a note but logically I think it makes sense to put this in another call to expects instead of in the final callback. This function can also be re-used, so I tend to put it somewhere reusable when possible: var isValidOrg = function(res) { res.body.should.have.property(“name”, “new_org”); … Read more
There is built-in assertion for this in supertest: should = require(‘should’) request = require(‘supertest’) app = require(‘../../app’) describe ‘authentication’, -> describe ‘POST /sessions’, -> describe ‘success’, -> it ‘redirects to the right path’, (done) -> request(app) .post(‘/sessions’) .send(user: ‘username’, password: ‘password’) .expect(302) .expect(‘Location’, ‘/home’) .end(done)
Tried to put this in a comment above, formatting wasn’t working out. I’m using async, which is really standard and works really well. it(‘should respond to only certain methods’, function(done) { async.series([ function(cb) { request(app).get(“https://stackoverflow.com/”).expect(404, cb); }, function(cb) { request(app).get(‘/new’).expect(200, cb); }, function(cb) { request(app).post(“https://stackoverflow.com/”).send({prop1: ‘new’}).expect(404, cb); }, function(cb) { request(app).get(‘/0’).expect(200, cb); }, function(cb) { … Read more
If i remember correctly in superagent one can pass a hash to set agent.set({key:value,key2:value2}) let me know if it doesnt work with supertest.
Although supertest is not that well documented, you can have a look into the tests/supertest.js. There you have a test suite only for the query strings. Something like: request(app) .get(“https://stackoverflow.com/”) .query({ val: ‘Test1’ }) .expect(200, function(err, res) { res.text.should.be.equal(‘Test1’); done(); }); Therefore: .query({ key1: value1, … keyN: valueN }) should work.
As zeMirco points out, the underlying superagent module supports sessions, automatically maintaining cookies for you. However, it is possible to use the superagent.agent() functionality from supertest, through an undocumented feature. Simply use require(‘supertest’).agent(‘url’) instead of require(‘supertest’)(‘url’): var request = require(‘supertest’); var server = request.agent(‘http://localhost:3000’); describe(‘GET /api/getDir’, function(){ it(‘login’, loginUser()); it(‘uri that requires user to be … Read more