Here’s the Deal

Jasmine vs BusterJS

50 9

2 0

When comparing Jasmine vs BusterJS, the Slant community recommends Jasmine for most people. In the question“What are the best JavaScript unit testing tools?” Jasmine is ranked 2nd while BusterJS is ranked 9th. 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 unit testing tools?

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
Supports deferring tests

No need to comment out your entire test case, now that you have Buster, which supports deferring a test so it doesn't actually run, but you get notified that there’s a deferred tests every time you run your test suite.

Pro
Flexible; extend it to wrap other test-frameworks

Have your test cases written in another framework, want to use BusterJS to run the tests, then you're in luck. BusterJS can be easily wrapped around other test frameworks. If you need to know how to do it, here's a link that showing just that.

Pro
Has support for NodeJS testing.

Working on a NodeJS app? BusterJS can help you Unit test it. This pretty much works just like browser tests, but you need to require Buster.JS in your tests.

Pro
You have the option of either running tests headless or via the browser

Don't have time to go through the lengthy process of opening up your browsers? BusterJS gives you the option of performing Headless tests. These are powered by PhantomJS; hence all your testing is done within the command line.

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
Has no plugins for major IDE's (Eclipse/IntelliJ) yet.

Do you prefer running your test cases from inside your IDE? well BusterJS will make that a lot difficult for you if not impossible. You'll have to run Buster using the good old way of spawning up a new terminal for running the tests.