to the 
Visit us on Discord or Discourse to give us some feedback or chat.
Pro Supports different assertion libraries
Mocha runs independently from the assertion library, so you can choose which assertion format works best for you. Mocha most often is run in combination with assertion library Chai.
Pro Write tests with Behavior Driven Development (BDD)
Allows developers to choose their development process. Not only TDD but also BDD.
Pro Integrates really well with NodeJS
The Mocha test framework itself runs on NodeJS, hence it makes everything related to it extremely simple. With Mocha's simple syntax and speed, testing your node.js app just got a whole lot easier.
Con No atomic tests
Tests cannot be ran in random order.
Con Can be intimidating for beginners
While some testing frameworks are complete out of the box, Mocha requires developers to select and set up assertion libraries and mocking utilities. For someone who is just starting to learn how to build tests this can be scary as they will also have to choose which libraries to use and learn them...
Pro Simple API
Very simple API that doesn't require globals, or monkey patching objects for assertions.
Pro It follows the principles of TAP
TAP: Test Anything Protocol
Con No concurrency
Cannot run async test cases concurrently for faster test builds.
Pro Recommended for React testing
Jest is the recommended unit testing framework by Facebook. It's also the one used by Facebook developers when working with React projects.
Con The official documentation is hard to understand
Like almost everything else release by Facebook (unfortunately), Jest has terrible documentation. It has a very basic example where everything is explained poorly. It doesn't explain most concepts or how everything fits together.
Pro Behaviour Driven Development focused
If you prefer your test cases and application to be developed from the perspective of your stake holders, Jasmine is the framework for you.
Pro Allows both DOM-less as well as Asynchronous testing
If you have some test cases that do not involve testing of DOM elements or events, those are exactly the ones where you want to use Jasmine. It'll provide smooth, simple and easy DOM-less testing of those test cases.
Con Not much room for flexibility
Jasmine comes with everything already baked in (including assertion libraries and mocking utilities). While this is great for beginners and people who don't want to spend much time looking into different libraries and tools it can be a turnoff for anyone who wants to use a different assertion...
Pro No globals
Doesn't use globals.
Know any negative aspects of this option?
Pro Extremely easy to start from scratch
All you have to do is to include the QUnit library either from the CDN or from the local server and then create your testcases.js file and run it. The outputs will be displayed in a nice format in the browser.
Pro Tests run in the order they're added to the suite
If you want your tests to run in the order you have provided (maybe if your tests are ordered in such a way that your current test relies on the previous one), you can do so by setting QUnit.config.reorder = false and the tests will run in the order that you have provided.
Con Doesn't support source maps
QUnit has no support for sourcemaps.
Con Testing of Async operations can be a little tough at times
QUnit expects you to call start() before an async function and stop() once it has stopped. This can be problematic when you have no way of knowing when exactly your function will start or stop.
Comments
Welcome to the Slant Community
Stop spending hours researching
Slant is written by a community helping you be informed. Let us know what you’re passionate about to get an awesome personalized feed.