23 August 2012
Hello! My original post was on http://chill.manilla.com, but since Manilla has been shutdown I have moved it here. It has not been updated, but is still a viable working strategy for javascript testing.

Getting setup with Javascript testing is not an easy task, but a framework like Jasmine makes it a lot less painful. However, when we enabled the asset pipeline on manilla.com, we also wanted to take full advantage of CoffeeScript. CoffeeScript is a great abstraction on Javascript and we wanted to leverage those benefits anywhere we could in our application and our tests. Our goals in utilizing CoffeeScript were:

  1. Write Jasmine tests against CoffeeScript and SCSS assets
  2. Write Jasmine tests in CoffeeScript
  3. Port existing Javascript Code to CoffeeScript
  4. Our first steps were to setup the infrastructure to perform testing with and against CoffeeScript files. Then we migrated our existing javascript source files to CoffeeScript.

CoffeeScript Enabled Testing & Continuous Integration (CI)

Our existing Jasmine tests used the jasmine-gem. The jasmine-gem worked well when we used static javascript files before adopting the asset pipeline. The existing Jasmine runner would run a standalone Rack webserver to serve static javascript files. Now, we wanted to allow both the tests and source files to be written in CoffeeScript and to load other precompiled assets like SCSS, so we re-evaluated our options. These are some of the gems available to accomplish this:

We chose the solution we thought was simple and we could easily support: jasminerice. The simplicity of utilizing the Rails Asset Pipeline to compile any assets, not just CoffeeScript, but also SCSS files made it ideal to run our Jasmine tests. To get started you have to:

  1. include jasminerice gem in the dev and testing groups
  2. edit your jasmine spec manifest in spec/javascripts/spec.js.coffee to include your test files (optionally include any scss/sass files in spec/javascripts/spec.css)
  3. write your tests in CoffeeScript including any dependencies
  4. visit http://localhost:3000/jasmine and watch your tests run

Running the jasmine tests headless for CI requires some additional help. We leveraged guard-jasmine which uses phantomjs & therubyracer to perform headless testing.

Migration from Javascript to CoffeeScript

Our migration path to CoffeeScript was to start with a few small examples and then move incrementally. When changes would occur in our javascript files in features, it would be the job of the developer to convert the file and any tests over to CoffeeScript. We utilized tools like js2coffee for larger files, but be warned it’s not perfect.


Setting up our Jasmine testing framework to work seamlessly with the asset pipeline with jasminerice was a major success. CoffeeScript and Jasmine tests are a great combination and make it very easy to understand. For more information on setting up jasminerice check out this railscast or the guard jasmine documentation.

Read more »