The easiest thing to do would be to use the built in promises support Mocha has in recent versions: it(‘Should return the exchange rates for btc_ltc’, function() { // no done var pair=”btc_ltc”; // note the return return shapeshift.getRate(pair).then(function(data){ expect(data.pair).to.equal(pair); expect(data.rate).to.have.length(400); });// no catch, it’ll figure it out since the promise is rejected }); Or … Read more
It’s pretty simple. You’re trying to test the wrapper component generated by calling connect()(MyPlainComponent). That wrapper component expects to have access to a Redux store. Normally that store is available as context.store, because at the top of your component hierarchy you’d have a <Provider store={myStore} />. However, you’re rendering your connected component by itself, with … 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
The differences are documented there. The three interfaces present different styles of performing assertions. Ultimately, they perform the same task. Some users prefer one style over the other. This being said, there are also a couple technical considerations worth highlighting: The assert and expect interfaces do not modify Object.prototype, whereas should does. So they are … 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
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
The rewire module is definitely the answer. Here’s my code for accessing an unexported function and testing it using Mocha. application.js: function logMongoError(){ console.error(‘MongoDB Connection Error. Please make sure that MongoDB is running.’); } test.js: var rewire = require(‘rewire’); var chai = require(‘chai’); var should = chai.should(); var app = rewire(‘../application/application.js’); var logError = app.__get__(‘logMongoError’); … Read more
You can either set the timeout when running your test: mocha –timeout 15000 Or you can set the timeout for each suite or each test programmatically: describe(‘…’, function(){ this.timeout(15000); it(‘…’, function(done){ this.timeout(15000); setTimeout(done, 15000); }); }); For more info see the docs.
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.
For expect, .equal will compare objects rather than their data, and in your case it is two different arrays. Use .eql in order to deeply compare values. Check out this link. Or you could use .deep.equal in order to simulate same as .eql. Or in your case you might want to check .members. For asserts … Read more