You have to specify the callback done as the argument to the function which is provided to mocha – in this case the it() function. Like so: describe(‘api’, function() { it(‘should load a user’, function(done) { // added “done” as parameter assert.doesNotThrow(function() { doRequest(options, function(res) { assert.equal(res, ‘{Object … }’); // will not fail assert.doesNotThrow … Read more
You can simply spy to the method directly via the prototype. it(“responds to name change”, done => { const handleChangeSpy = sinon.spy(New.prototype, “handleChange”); const event = {target: {name: “pollName”, value: “spam”}}; const wrap = mount( <New /> ); wrap.ref(‘pollName’).simulate(‘change’, event); expect(handleChangeSpy.calledOnce).to.equal(true); }) Alternatively, you can use spy on the instance’s method, but you have to … Read more
Testing in ES6 with Mocha and Babel 7. Look here: https://dev.to/bnorbertjs/my-nodejs-setup-mocha–chai-babel7-es6-43ei or http://jamesknelson.com/testing-in-es6-with-mocha-and-babel-6/ npm install –save @babel/runtime npm install –save-dev @babel/plugin-transform-runtime And, in .babelrc, add: { “presets”: [“@babel/preset-env”], “plugins”: [ [“@babel/transform-runtime”] ] }
You don’t. Karma is only for testing browser-based code. If you have a project with mocha tests on the backend and karma/mocha on the front end, try editing your package.json under scripts to set test to: mocha -R spec && karma run karma.con Then, if npm test returns true, you’ll know it’s safe to commit … Read more
Use this: mocha server-test Or if you have subdirectories use this: mocha “server-test/**/*.js” Note the use of double quotes. If you omit them you may not be able to run tests in subdirectories.
It is much preferable to keep the tests isolated so that one test does not depend on a computation performed in another. Let’s call the test that should pass a value test A and the test that should get it test B. Some question to consider: Are test A and test B really two different … Read more
Just drop .then(done); and replace function(done) with function() You are returning a Promise so calling done is redundant as it said in error message In the elder versions you had to use callback in case of async methods like that it (‘returns async’, function(done) { callAsync() .then(function(result) { assert.ok(result); done(); }); }) Now you have … Read more
If you want to include multiple modules into your describe hierarchy like you are doing in your question, what you are doing is pretty much it, unless you want to write a custom test loader for Mocha. Writing the custom loader would not be easier or make your code clearer than what you already have. … Read more
I know an ugly way of doing it, just by increasing default timeout of Mocha from 2 seconds to 10 seconds this can be done by adding a flag –timeout 10000 in the test scripts i.e – package.json “scripts”: { “start”: “SET NODE_ENV=dev && node server.js”, “test”: “mocha –timeout 10000” }
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