A lovely javascript testing framework -- want to contribute? join us in https://gitter.im/mochajs/contributors
Hmmm, I don't know one off hand nor do I have one for any of my current projects. Maybe someone else can point you in the right direction.
One idea may be that your ignore may need beginning slash to indicate its a directory
"ignore": ["/node_modules"]Another workaround would be to just point mocha to your tests directory, if you keep all of your tests under one directory that is:
"spec": ["./src/tests/**/*.spec.js"],
Hello all! I have been running around SO, mocha source, issues, and any other tutorials I can find, but I am still doing something wrong...
I'm executing mocha programmatically, within node, so I know this is atypical. However, I must be missing something someone with more experience than me knows about. Suffice it to say, in one file I want to export a describe block with a couple of its inside. In another file I want to export another describe block (or maybe just a solo it test).
At my entrypoint I instantiate:
const mocha = new Mocha({
delay: true,
timeout: 30000,
ui: 'bdd',
});
mocha.suite.addSuite(someSuite);and in the same file I execute mocha.run(). When I run my script, (node src/index.ts), I get the following error:
TypeError: mocha_1.describe is not a functionmocha /tests/**.spec.js", or similar approaches where the goal was to run a test multiple times from a file (and the resulting solution involved clearing the require cache). Nobody has really offered any kind of tips or ideas on how to run with node :/
Whoops. Neglected to mention in my last message, my script does include node -r ts-node/register src/index.ts
Does thists-node/register requirement mean I'm suffering from the same require cache not-bug that other folks have discussed??
Here's an example of a describe that is failing:
import { expect } from 'chai';
import { describe } from 'mocha';
export default describe('this is a parent test suite', function () {
it (`does something`, () => {
expect(true).to.be.true;
});
it (`does another thing`, () => {
expect(1).to.equal(1);
});
});I assume my index's import Mocha from 'mocha'; is causing some kind of issue with accessing these interface functions appropriately. I see that describe was given the warning:Only available when invoked via the mocha CLI.
but... that's gotta be baloney
mocha.addFiles(myspecs);?
describe wrapped in a func as well
Hello to all! Yesterday I asked a question about configuring mocha to use two compilers: coffeescript and babel (for ES6 features). With help of @craigtaub the solution was found. It was to require a setup file written in JS via command line argument:
mocha --require ./setup.js test_file_ES6.coffeesetup.js is
const register = require('@babel/register').default;
require('coffeescript/register');
register({ extensions: ['.coffee', '.js'] });This worked perfectly and my test_file_ES6.coffee was executed.
Now there is another problem: when in test_file_ES6.coffee I'm importing a nodejs module my_common_package it is not compiled by babel: in command line I see error like:
/home/name/work/projects/alpha/my_common_package/src/coffee/file.coffee:3
import * as translations from './translations.coffee';
^^^^^^
SyntaxError: Unexpected token importCould someone help with this?
I have built a chain of imports to check if importcommand failed immedeately after the first import.
it looks like this:test_file_ES6.coffee imports test_import1.coffeetest_import1.coffee imports test_import2.coffee
and the last file does the import of my_common_package
and the error was at the same place as above: /home/name/work/projects/alpha/my_common_package/src/coffee/file.coffee:3
pretty strange
there is a kind of a solution. to use this setup.js which required by mocha:
var defaultOptions;
defaultOptions = {
sourcemap: true,
transpile: {
env: {
development: {
sourceMaps: 'inline',
plugins: ['source-map-support']
}
},
presets: ["@babel/preset-env"]
}
};
require('module').prototype.options = defaultOptions;
require('source-map-support/register');
require('coffeescript/register');
module.exports = function(options) {
require('module').prototype.options = options != null ? options : {};
require('source-map-support/register');
return require('coffeescript/register');
};with this config there are no errors with import keyword but the sourcemaps became broken and the bugsearching in tests' source code become a real headache
Anyone interested in an opensource project?
Spec oriented development speeds up programming by generating code based on tests/specs. Tests required will be the same or less specs as a normal developer writes.
https://github.com/Neur0plasticity/spec-dev
MSG me if interested
--delay option? I need delay to perform setup for mongo-unit. My setup works in a local env, but in circleci it doesn't find any tests when delay is set. Have played with it a bit on circleci via ssh, I can see that my init.spec.js is executing but the callback from the async call therein (to start mongo-unit) never fires. The call to mocha::run is in that callback so I guess that's why it's not running any tests. Wondering if anyone has encountered similar?
Hey guys I have started using mocha with selenium and when I try to click on certain element I get this error:
ElementNotInteractableError: element not interactable
(Session info: chrome=78.0.3904.108)
at Object.throwDecodedError (node_modules\selenium-webdriver\lib\error.js:550:15)
at parseHttpResponse (node_modules\selenium-webdriver\lib\http.js:563:13)
at Executor.execute (node_modules\selenium-webdriver\lib\http.js:489:26)
at process.internalTickCallback (internal/process/next_tick.js:77:7)
