Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 11 14:51
    New Donation: CodeFund gave USD 6.91 to MochaJS! [Thank that person on Twitter]
  • Nov 11 13:31
    juergba labeled #4091
  • Nov 11 13:31
    juergba unlabeled #4091
  • Nov 11 11:09
    basickarl edited #4091
  • Nov 11 11:02
    basickarl edited #4091
  • Nov 11 10:59
    basickarl labeled #4091
  • Nov 11 10:59
    basickarl opened #4091
  • Nov 11 07:56
    Alhadis closed #3937
  • Nov 10 19:49
    stale[bot] labeled #3833
  • Nov 09 19:32
    New Donation: Cosmin Olteanu gave USD 5 to MochaJS!
  • Nov 09 07:49
    stale[bot] closed #3973
  • Nov 09 01:00
    MicahZoltu labeled #4090
  • Nov 09 01:00
    MicahZoltu opened #4090
  • Nov 08 10:24

    Munter on npm-funding

    (compare)

  • Nov 07 20:52
    boneskull milestoned #4089
  • Nov 07 20:52
    boneskull labeled #4089
  • Nov 07 20:52
    boneskull labeled #4089
  • Nov 07 20:52

    boneskull on master

    Add funding information to pack… (compare)

  • Nov 07 20:52
    boneskull closed #4089
  • Nov 07 08:51
    Munter review_requested #4089
Thomas Scholtes
@geigerzaehler
@juergba: I created this issue: mochajs/mocha#4016.
It is a very narrow case that has a workaround and was an issue before. It’s quite hard to fix properly
Juerg B.
@juergba
@geigerzaehler thanks
@solaris765 could you add your case to this issue, please?
Mason Rhodes
@solaris765
@juergba @geigerzaehler I've added my specific case to 4016. And thanks for the work around for now. As far as I can tell, for now anyways, --recursive may be better left to final testing before deployments as opposed to a during development tool with the watcher at least.
kundol
@wnghdcjfe
Hi
raghanag
@raghanag
Hi All
how to specify a js file which loads the all the libs using requirejs with ts-mocha option
Craig Taub
@craigtaub

@raghanag ts-mocha is a wrapper over mocha so not sure if completely follow that part. if its a TS issue we have an example TS mocha here https://github.com/mochajs/mocha-examples/tree/master/typescript.

The other part of ur question, u can create a load-libs.js file which requires all your libs and use mocha —require load-libs.js to load them before tests.
Does this help? if not pls supply more details about problem.

raghanag
@raghanag
@craigtaub thanks
raghanag
@raghanag
can you give me a sample of the load-libs.js file
raghanag
@raghanag
can i use .mocharc.json to load all the libs required by my spec files to load
Craig Taub
@craigtaub

@raghanag you can use .mocharc.json to load a single file which itself requires all other libs.
load-libs.js

require("@babel/register”);
require(“some-other-lib”);

does that help?

Beka Iglesias
@geekshabeka_twitter
Hello! I am using mocha + chai to wirte unit tests for my node Rest API
I need to launch node server.js with two parameters
my tests are failing to launch because of they are missing the parameters
how can I say to mocha + chai that launch app with parameters when I do npm test as it do when I do npm start?
I use mocha before but it's the first time that I need to indicate parameters because in this case part of the endpoints are a wrapper for another java server
Craig Taub
@craigtaub
@geekshabeka_twitter if mocha is launching the app, you can pass params to mocha like env KEY=MINE mocha and use process.env.KEY from inside your test code. Hope that helps
Beka Iglesias
@geekshabeka_twitter
Thanks for the answer.I will try it
Veera Subba Reddy
@subbulomada_twitter
Hi All, Can some help on the below issue. I am seeing TypeError: $(..).waitForExist
setValue is not a function.
I am using JavaScript with mocha framework
Jacob Bogers
@Jacob_Bogers_twitter
hi
is setup(...)function part of the mocha test library, I am looking at some code 4yo, and It seems this is part of mocha?
Peter Müller
@Munter
@Jacob_Bogers_twitter It's part of the TDD interface. https://mochajs.org/#tdd
Jacob Bogers
@Jacob_Bogers_twitter
Hi @Munter thanks for answering, just figured it out
my real problem was the my IDE (vscode) was marking "suite" as unknown global, I just had the add { "env":"mocha"} and plugins: ["mocha"] to the eslintrc file
now my IDE isn't screaming anymore
Armin Ayari
@mrastiak
Hello everyone
How can I skip all the remaining test cases in a test suite after one of the test cases fails
Craig Taub
@craigtaub
@mrastiak test cases should really work in isolation and not depend on each others results. So they should be put into the state they require in order to run your tests.
Peter Müller
@Munter
Someone has made a library that gives you this functionality. https://www.npmjs.com/package/mocha-steps
But generally I agree with @craigtaub . Wouldn't recommend using it
Armin Ayari
@mrastiak
@craigtaub Thank you for the fast reply
What I'm testing is the procedure of buying a product and if a step fails the rest of the steps will fail too
Every step here is a test case and creating a test suite for each step with one test case looks like a bad idea to me
Peter Müller
@Munter
You might want to look into other test runners that are purpose-built for this. Like Selenium, Cypress and other browser runners
raghanag
@raghanag
Hi @craigtaub i am using mocha with ts-node to test the spec files written in typescript, i am getting the cannot find module errors when my source file is importing some modules. can you help me here
i am using the below command to run the mocha
    "test:unit": "TS_NODE_PROJECT='components/src/tsconfig.mocha.json' mocha -r ts-node/register components/src/**/*.spec.ts"
and the error
components/src/list-filter/list-filter-viewModel.ts:6:35 - error TS2307: Cannot find module 'ojL10n!./resources/nls/list-filter-strings'.

6 import * as componentStrings from 'ojL10n!./resources/nls/list-filter-strings';
Dave Chappelle
@davidchappelle
Looking for some insights into a problem I have run into several times now. The project that I am working on has a fairly large and growing number of test suites. Occasionally, tests get checked in that cause things like timers and the like to be armed leaving the event loop in a state where it won't exit cleanly. After thousands of tests run, mocha is just left hung at the end of its execution. I typically use wtfnode to track these issues down. However, it would be handy if mocha provided a mechanism by which you could enforce that every test or test suite finished without leaving crap on the event loop. Does such a mechanism exist? Ideally I wouldn't have to litter a bunch of boilerplate around.
Gil Tayar
@giltayar
Hi everybody. I've been wanting to add support for native Node ESM modules in Mocha for quite some time, but the experimental support wasn't very stable (in terms of spec). Now that it's stabilizing, I've started working on a PR for this. Is this something y'all would like to see? This is not a trivial change, as it means turning loadFiles into an async (promise returning) function, and, from what I'm seeing, all the run* stack too. This shouldn't be a problem, as Mocha supports Node>=8, which even has async/await support, but it is a significant change (which I would be glad to implement). Not sure about browser support for this, though. (does Mocha support IE?)
Peter Müller
@Munter
@giltayar mocha does support ie. But I think we could probably roll things up in a node and a browser build. Since the browser build will not be the one loading files it might just work. I don't have much experience with building separate esm, commonjs and browser builds though, do I don't know the potential problems
Gil Tayar
@giltayar
Hmm... I'll have to look at the browser build then. Currently, from what I'm seeing, broeserify
From what I'm seeing, browserify
Is definitely trying to read the loadFiles method. Maybe I can separate that somehow. (sorry For the multiple messages. Mobile...)
But it's not a small endavour, and I'd like to know whether I will be getting any basic objections to node ESM support, before I start working on this.
Peter Müller
@Munter
Not from me. But I'm not the biggest proponent of the conservative browser support range we keep. Would you mind joining mochajs/contributors for this discussion?
Gil Tayar
@giltayar
Would love to. Just join the room and ask? (not sure about the etiquette...)
Peter Müller
@Munter
Yeah, I'm pretty sure it's open for all that want to join.
Craig Taub
@craigtaub
@raghanag is ojL10n!./resources/.. definitely the right path name? ojL10n!. does not look right as a lib.
Perhaps setup and supply us an MCVE (https://stackoverflow.com/help/minimal-reproducible-example).
raghanag
@raghanag
@craigtaub i figured out that I have to use @modulealiases package to resolve the paths when using typescript in node