Here’s the Deal

Jasmine vs livedoc-mocha

50 9

1 0

When comparing Jasmine vs livedoc-mocha, the Slant community recommends Jasmine for most people. In the question“What are the best JavaScript BDD frameworks?” Jasmine is ranked 2nd while livedoc-mocha 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.

Ranked in these QuestionsQuestion Ranking

Common Questions

What are the best JavaScript BDD frameworks?

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
Great looking test output

Pro
Loads of options and create your own reports if needed

You can create your own reports as it can output the results in JSON. Not done it ourselves yet, but could be useful.

Pro
Powerful implementation of the Gherkin Spec

Ad
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
Not great for Teams that don't value testing

As this takes more effort (ie you need to think harder about the test/spec) to write good tests. We found some team members didn't like it. If your team thinks tests are a tax, better to go with a simpler option like mocha.