Mocha has support for ESM from version 7.1.0 onward (release: Feb. 26, 2020). This requires Node 12.11.0 or higher, and is subject to the current restrictions/limitations of using modules in Node: Either you must use .mjs file extensions for source files that use ES modules, or you must have “type”: “module” in your package.json You … Read more
There are a few options available to you: Option 1: Use JSDOM By adding a DOM to your code, you can unit test much of your client-side code within node.js Option 2: Use MOCHA on the client Mocha does run inside the client and you can use separate client-side unit tests. This tends to be … Read more
Enzyme’s mount takes optional parameters. The two that are necessary for what you need are options.context: (Object [optional]): Context to be passed into the component options.childContextTypes: (Object [optional]): Merged contextTypes for all children of the wrapper You would mount SampleComponent with an options object like so: const store = { subscribe: () => {}, dispatch: … Read more
If you can guarantee that the event should fire within a certain amount of time, then simply set a timeout. it(‘should emit an some_event’, function(done){ this.timeout(1000); //timeout with an error if done() isn’t called within one second myObj.on(‘some_event’,function(){ // perform any other assertions you want here done(); }); // execute some code which should trigger … Read more
In my case, I developed a library last time that use ioredis as peer dependency. My solution was to put that library as well in dev dependency. // package.json “peerDependencies”: { “ioredis”: “4.x” }, “devDependencies”: { “ioredis”: “4.x” } it worked well and no issue so far using this approach.
I had the same issue when accidentally using fakeAsync in a describe function. Removed it solved the issue for me.
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
Here is an alternative and non order dependent approach for collections: array expect([1, 2, 3]).to.include.members([3, 2, 1]) You can also use this with a deep flag for comparison of objects: array of objects expect([{ id: 1 }]).to.deep.include.members([{ id: 1 }]); object expect({foo: ‘bar’, width: 190, height: 90}).to.include({ height: 90, width: 190 })
Mocha loader won’t run tests while building, it’s used to create a bundle specifically containing your tests which you can then run from your browser. I would recommend creating a separate webpack config file for your tests, which you can then host on a webpack-dev-server that uses a different port from your application. Here’s an … Read more
The –recursive flag is meant to operate on directories. If you were to pass a glob that matches directories, then these directories would be examined recursively but if you pass a glob that matches files, like you are doing, then –recursive is ineffective. I would suggest not using –recursive with a glob because globs already … Read more