The it call identifies each individual tests but by itself it does not tell Mocha anything about how your test suite is structured. How you use the describe call is what gives structure to your test suite. Here are some of the things that using describe to structure your test suite does for you. Here’s … Read more
I don’t think Mocha itself supports passing extra parameters to your tests, but you could use environment variables: env KEY=YOUR_KEY mocha test/*.js # assumes some sort of Unix-type OS. And read them in your test files: var key = process.env.KEY;
Most of the answers here seem to address primarily Babel. With anything else like eslint, tslint etc. and pure Typescript it’s enough to add @testing-library/jest-dom to your types. So a few quick steps: Make sure you’ve got the library installed: yarn add -D @testing-library/jest-dom or npm i @testing-library/jest-dom –save-dev and then link it in your … 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
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
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
Since the answer that works for a lot of people appears to be hidden in the comments, I’ll post it as an actual answer to the question, now that it appears the question has been reopened. I had this problem as well. Not sure why this Q has been closed. but installing ts-node locally fixes … Read more
You’re not passing your function to assert.throws() the right way. The assert.throws() function expects a function as its first parameter. In your code, you are invoking iThrowError and passing its return value when calling assert.throws(). Basically, changing this: assert.throws(iThrowError(), Error, “Error thrown”); to this: assert.throws(iThrowError, Error, “Error thrown”); should solve your problem. With args: assert.throws(() … Read more
since npm 5.2.0, there’s a new command “npx” included with npm that makes this much simpler, if you run: npx mocha <args> Note: the optional args are forwarded to the command being executed (mocha in this case) this will automatically pick the executable “mocha” command from your locally installed mocha (always add it as a … Read more
before() is run once before all the tests in a describe after() is run once after all the tests in a describe beforeEach() is run before each test in a describe afterEach() is run after each test in a describe Which one you want to use depends on your actual test. Now, for … Read more