You should run Mocha with the –delay option, and then use run() once you are done building your test suite. Here is an example derived from the code you show in the question: ‘use strict’; function test() { console.log(1); describe(‘Unit Testing’, () => { console.log(2); it(“test”, () => { console.log(3); }); }); // You must … Read more
You can skip tests by placing an x in front of the describe or it block, or placing a .skip after it. xit(‘should work’, function (done) {}); describe.skip(‘features’, function() {}); You can also run a single test by placing a .only on the test. for instance describe(‘feature 1’, function() {}); describe.only(‘feature 2’, function() {}); describe(‘feature … Read more
For Babel <6 The easiest way to solve this problem is: npm install babel-preset-es2015 –save-dev Add .babelrc to the root of the project with contents: { “presets”: [ “es2015″ ] } Ensure that you are running mocha with the “–compilers js:babel-core/register” parameter. For Babel6/7+ npm install @babel/preset-env –save-dev Add .babelrc to the root of the … Read more
I’ve started employing the import * as obj style within my tests, which imports all exports from a module as properties of an object which can then be mocked. I find this to be a lot cleaner than using something like rewire or proxyquire or any similar technique. I’ve done this most often when needing … Read more
Your asynchronous test generates an exception, on failed expect()ations, that cannot be captured by it() because the exception is thrown outside of it()‘s scope. The captured exception that you see displayed is captured using process.on(‘uncaughtException’) under node or using window.onerror() in the browser. To fix this issue, you need to capture the exception within the … Read more
There are two main problems here. The first is of course that you need to fix your import problem, but that is unrelated to testing. You will need to resolve this before going into testing, and this might have to do with the configuration of your build tool versus running in Node. You should open … Read more
For new mocha versions : You can now return a promise to mocha, and mocha will wait for it to complete before proceeding. For example, the following test will pass : let a = 0; before(() => { return new Promise((resolve) => { setTimeout(() => { a = 1; resolve(); }, 200); }); }); it(‘a … Read more
Here you go: http://mochajs.org/#test-level it(‘accesses the network’, function(done){ this.timeout(500); [Put network code here, with done() in the callback] }) For arrow function use as follows: it(‘accesses the network’, (done) => { [Put network code here, with done() in the callback] }).timeout(500);
A prettier way to do this, is to export both your plain component, and the component wrapped in connect. The named export would be the component, the default is the wrapped component: export class Sample extends Component { render() { let { verification } = this.props; return ( <h3>This is my awesome component.</h3> ); } … Read more
By default Mocha will read a file named test/mocha.opts that can contain command line arguments. So you could create such a file that contains: –timeout 5000 Whenever you run Mocha at the command line, it will read this file and set a timeout of 5 seconds by default. Another way which may be better depending … Read more