briangershon/headless-jasmine-boilerplate

This is a starting place for those wanting to run headless Jasmine JavaScript tests locally, on their CI server or on Travis CI.

Headless Jasmine Boilerplate

This is a starting place for those wanting to learn how to run headless Jasmine JavaScript tests locally and on Travis CI.

Once you're familiar with how it works, it should be easy to add to your own projects.

Project includes:

• how to setup Jasmine gem

• sample Jasmine layout, created via jasmine init

• tweak of Rakefile to use 'jasmine:ci' task by default (for Travis and other CI systems)

• Travis CI integration via .travis.yml -- see Travis CI Getting Started

Setup and seeing test runner in action

1. Clone this repository

2. Ruby should already be installed on your system. Or install via Homebrew (on OSX). Or use Ruby Version Manager (https://rvm.io) if you want to isolate these Ruby dependencies.

3. Make sure you're in the root of the repository (which contains the gem and rake files)

4. Install dependencies using bundler

    # run 'gem install bundler' if you don't already have bundler
    bundle install
   

5. Run tests

    bundle exec rake jasmine    # for a local web server version at http://localhost:8888
    bundle exec rake            # for default headless CI version. See "How to run headless" below.
   

How to run headless (for Continuous Integration)

Headless CI requires additional dependencies.

If running on your own desktop, just install Firefox.

If running on a server:

1. a virtual framebuffer such as Xvfb

2. a headless DOM via such as iceweasel on Ubuntu (which is headless Firefox), PhantomJS, etc.

Travis CI has these dependencies installed (see .travis.yml file). If you're running your own CI server, you'll need to install these.

Are we running ok on Travis CI?

Helpful resources

• New to Jasmine? Take a Quick Tour. See also the "Matchers" reference (Jasmine's equivalent to asserts).

• Writing a CoffeeScript web application using TDD

• Javascript Loves CI

• Travis CI Docs

Why Jasmine?

• enjoyable to use and easy to pickup. BDD-styled tests have nice readability.

• well supported, well maintained.

• JavaScript platform agnostic -- works fine with the JS libraries you're already using (jQuery, Closure Library, require.js, etc).

• popular in the industry. Used by Cordova/PhoneGap for example.

• easy (easiest?) to run headless on server (via Jasmine Ruby Gem and a few dependencies).

• has spies and mocks built-in. There's also the Sinon.js library.