Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Jasmine vs tape, the Slant community recommends Jasmine for most people. In the question“What are the best JavaScript unit testing frameworks?” Jasmine is ranked 3rd while tape is ranked 5th. The most important reason people chose Jasmine is:
If you prefer your test cases and applications to be developed from the perspective of your stake holders, Jasmine is the framework for you.
Question Ranking
Pros
Pro Behaviour Driven Development focused
If you prefer your test cases and applications to be developed from the perspective of your stake holders, Jasmine is the framework for you.
Pro Easy to find Jasmine tutorials for most MV* frameworks,
whilst Mocha is still considered the new kid on the block.
Pro Has a very readable and user-friendly syntax
Code readability is an important factor, if the application development involves multiple teams; if the testing team is unable to read your test cases then they won't be able to test it. Jasmine resolves this issue by providing developers with an extremely simple and "human-friendly" syntax.
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.
Pro Integrates very well with Ruby on Rails
The jasmine-rails gem allows you to run Jasmine specs in a browser (powered by Rails engine mounted into your application).
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.
Pro No global functions
Tape does not use global methods such as "it", "describe", since they are not considered best practice in JavaScript.
Pro It follows the principles of TAP
TAP: Test Anything Protocol
Cons
Con Maintainers are not very responsive to pull requests
Pivotal aren't responsive to pull requests, though they have made repo changes within < 3 months
Con No concurrency
Cannot run async test cases concurrently for faster test builds.
