found an alternative in connect.js tests suites They are using supertest to test a connect app without binding the server to any port and without using mock-ups. Here is an excerpt from connect’s static middleware test suite (using mocha as the test runner and supertest for assertions) var connect = require(‘connect’); var app = connect(); … Read more
Mocha supports any assertion library you want. You can take a look at how it deals with assertions here: http://mochajs.org/#assertions. I don’t know which one you want to use. Considering you are using Chai, which is pretty popular, here are some options: Consider “foo” to be the target variable you want to test Assert var … Read more
In the second file, require the first one: — two.js — require(“./one”) or if you are using ES modules: — two.js — import “./one” Mocha will run the tests in the order the describe calls execute.
A basic approach to run the same test with different data is to repeat the test in a loop providing the data: describe(‘my tests’, function () { var runs = [ {it: ‘options1’, options: {…}}, {it: ‘options2’, options: {…}}, ]; before(function () { … }); runs.forEach(function (run) { it(‘does sth with ‘ + run.it, function … Read more
I have done testing in both Jasmine and Mocha. First, switching is relatively easy. The basic describe and it BDD pattern is identical. You will need to change how you do your assertions and switch to a different interface for asynchronous tests. Overall they are comparable. Mocha’s asynchronous interface is much simpler and more consistent. … Read more
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
The problem with this approach is that (await fails()).should.throw(Error) doesn’t make sense. await resolves a Promise. If the Promise rejects, it throws the rejected value. So (await fails()).should.throw(Error) can never work: if fails() rejects, an error is thrown, and .should.throw(Error) is never executed. The most idiomatic option you have is to use Chai’s rejectedWith property, … Read more
There is a babel/register style hook to ignore style imports: https://www.npmjs.com/package/ignore-styles Install it: npm install –save-dev ignore-styles Run tests without styles: mocha –require ignore-styles
You can serialize simple data to check for equality: data1 = {firstName: ‘John’, lastName: ‘Smith’}; data2 = {firstName: ‘Jane’, lastName: ‘Smith’}; JSON.stringify(data1) === JSON.stringify(data2) This will give you something like ‘{firstName:”John”,lastName:”Smith”}’ === ‘{firstName:”Jane”,lastName:”Smith”}’ As a function… function compare(a, b) { return JSON.stringify(a) === JSON.stringify(b); } compare(data1, data2); EDIT If you’re using chai like you say, … Read more
Mocha is a test framework; you need to provide your own assertion lib as https://mochajs.org/#assertions states. Thus, expect is indeed undefined because you never defined it. (I recommend chai) npm install chai then (see Amit Choukroune’s comment pointing out to actually require chai) then var expect = chai.expect;