Skip to content

Latest commit

 

History

History
98 lines (57 loc) · 1.9 KB

README.md

File metadata and controls

98 lines (57 loc) · 1.9 KB
Raw

Jasminerice

Utilizing (jasmine)[http://pivotal.github.com/jasmine/] and taking full advantage of the Rails 3.1 asset pipeline jasmine rice removes any excuse YOU have for not testing your out of control sprawl of coffeescript files. This project rocks and uses MIT-LICENSE.

Headless Testing Via Guard-Jasmine

See (guard-jasmine)[http://rubydoc.info/github/guard/guard-jasmine/master/frames] for details

Setup For Rails 3.1

This is a gem specifically for Rails 3.1. Just include it in your Gemfile so

gem "haml" # Unless included elsewhere in your gemfile
gem "jasminerice"

The engine is automatically mounted into your application in the development and test environments. If you'd like to change that behavior, you can override the array Jasminerice.environments in an initializer.

Create a single file called

spec/javascripts/spec.js.coffee

with the following content

#=require_tree ./

This pulls in all your

spec/javascripts/*_spec.js.coffee
spec/javascripts/*_spec.js
spec/javascripts/*_spec.js.erb
etc

into jasmine. For example

spec/javascripts/foo.js.coffee

#= require foo
#= require bar

describe "Foo", ->

	it "it is not bar", ->
		v = new Foo()

		expect(v.bar()).toEqual(false)

describe "Bar", ->

	it "it is not foo", ->
		v = new Bar()

		expect(v.foo()).toEqual(false)

The Rails 3.1 asset pipeline using sprockets and tilt ensure conversion. As well you can use the #require dependency mechanisms

Now start your server

rails s

Goto

http://localhost:3000/jasmine

and there are your specs.

For including stylesheets in your specs, jasminerice uses a spec.css file. Create such a file next to the spec.js.coffee file:

spec/javascripts/spec.css

and in that file, use sprockets directives to include the right css files, e.g.

 /*
  *= require application
 */

Questions:

bradphelan@xtargets.com