to chai.
Slant community chat on DiscoursePro 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 Makes Asynchronous testing extremely easy
No need to write tricky statements for Async testing. Mocha gives you a done callback. Place this done parameter in your callback function, that'll let Mocha know that you've written an asynchronous function.
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...
Con No atomic tests
Tests cannot be ran in random order.
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.
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 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.
Know any negative aspects of this option?
Pro Simple API
Very simple API that doesn't require globals, or monkey patching objects for assertions.
Pro Built-in assert
This way you don't have to add more dependencies and external assertion libraries.
Con No concurrency
Cannot run async test cases concurrently for faster test builds.
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.
Pro No globals
Doesn't use globals.
Know any negative aspects of this option?
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.