mocha

Quite coincidentally ran across this survey from 2014 that shows Jasmine and Mocha are pretty much neck and neck.

You can specify a single test as your entry-point, and then point mocha to it.

Jasmine is widespread but Mocha is pretty much the norm for modules on NPM.

As a general rule, I'd say node-based projects are heavily mocha based, whereas browser-based projects are much more mixed.

I'm in the functional JS camp so Immutable.js, Ramda, and js-csp for libraries and I run mocha+chai for testing.

Btw, on JavaScript context I use accidentally mocha+should, not tape, just cause I discovered tape later...

This is in part because Mocha is considerably easier to instrument.

There is an active effort to split up Mocha into multiple modules in order to make it more portable, which would make the stubbing unnecessary, too.

And as a final data point, note that on NPM, the main mocha package has almost 5 times the weekly downloads of the main jasmine package.

A modern mocha/chai/sinon testing stack will be 100 times faster (I wish that was hyperbole), much more stable, and much better supported.

CoffeeScript based projects seem especially likely to use Mocha over Jasmine; Angular (as you noted) has a strong preference for Jasmine due to their Protractor tool, etc.

The only numbers I've seen suggest that it's mostly Mocha and Jasmine.

If you wanna use it in "live" mode, you can run webpack and mocha both with the watch flag.

Again, if you want "live" mode, you can set the watch flag on both mocha and webpack.

It's glacially slow and kind of buggy, and in my experience most projects using React use Mocha, not Jest.

So you need Mocha, or something very like it.

It was extremely straightforward to integrate with Mocha, though.