Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Guard::JasmineNode automatically runs your Jasmine Node specs when files are modified

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 lib
Octocat-spinner-32 spec
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .travis.yml
Octocat-spinner-32 CHANGELOG.md
Octocat-spinner-32 Gemfile
Octocat-spinner-32 Guardfile
Octocat-spinner-32 README.md
Octocat-spinner-32 Rakefile
Octocat-spinner-32 guard-jasmine-node.gemspec
README.md

Guard::JasmineNode travis-ci

JasmineNode guard automatically & intelligently executes jasmine node specs when files are modified.

It works brilliantly with Node projects whereas guard-jasmine looks better for jasmine specs in the context of e.g. a Rails app.

  • Tested against Node 0.8.9, jasmine-node 1.0.26

Requirements

Install

Install the gem:

$ gem install guard-jasmine-node

Add guard definition to your Guardfile by running this command:

$ guard init jasmine-node

Usage

$ guard

This will watch your project and execute your specs when files change. It's worth checking out the docs.

Options

  • :all_on_start # default => true

Run all the specs as soon as Guard is started.

  • :all_after_pass # default => true

When files are modified and the specs covering the modified files pass, run all the specs automatically.

  • :keep_failed # default => true

When files are modified, run failing specs as well as specs covering the modified files.

  • :notify # default => true

Display growl/libnotify notifications.

  • :coffeescript # default => true

Load coffeescript and all execution of .coffee files.

  • :forceexit # default => false

Force jasmine-node process to quit after test (can help fix hanging specs)

  • :verbose # default => false

Execute jasmine-node in verbose mode

  • :spec_paths # default => [spec]

Array of paths containing all specs (supply a comma-separated list of paths to override the default)

  • :jasmine_node_bin

Specify the path to the jasmine-node binary that will execute your specs.

The default :jasmine_node_bin in the Guardfile assumes:

  • you are running guard from the root of the project
  • you installed jasmine-node using npm
  • you installed jasmine-node locally to node_modules

If you delete the option completely from the Guardfile, it assumes the jasmine-node binary is already in your $PATH.

So if you have installed jasmine-node globally using e.g. npm install -g jasmine-node, remove the :jasmine_node_bin option from the Guardfile.

Guardfile

Please read the guard docs for more information about the Guardfile DSL.

It's powerful stuff.

Development

Pull requests are very welcome! Make sure your patches are well tested. Please create a topic branch for every separate change you make.

TODO

  • write a JsonFormatter for jasmine-node so we have finer-grained control over rendering output
  • write an RSpec-style progress formatter (aka lots of green dots)
  • patch Guard to locate CamelCased modules correctly

Testing

Ruby >= 1.9 required.

$ rake

Author

Dave Nolan

Something went wrong with that request. Please try again.