github-migration
/
guard-jasmine-headless-webkit
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

readme tweak

This commit is contained in:
John Bintz 2011-05-24 06:22:01 -04:00
parent 5b5b112ade
commit b2d4c3c2ea
1 changed files with 15 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -1,10 +1,22 @@
Whoa, it works with Guard! So fast! ## Guard support for jasmine-headless-webkit
Add running your Jasmine specs to your `Guardfile` via [`jasmine-headless-webkit`](http://github.com/johnbintz/jasmine-headless-webkit/). Nice!
guard 'jasmine-headless-webkit' do guard 'jasmine-headless-webkit' do
watch(%r{^app/assets/javascripts/(.*)\..*}) { |m| newest_js_file("spec/javascripts/#{m[1]}") } watch(%r{^app/assets/javascripts/(.*)\..*}) { |m| newest_js_file("spec/javascripts/#{m[1]}") }
end end
Guard options: ## `guard` options
* `:all_on_start => false` to not run everything * `:all_on_start => false` to not run everything, just like `guard-rspec`
## What's the deal with `newest_js_file`?
Since one could, theoretically, have a CoffeeScript app file and a JavaScript spec file (or vice versa), the search for the correct matching
file is a little more complicated. `newest_js_file` extends the Guard DSL to search the given path for the newest `.js` or `.coffee` file:
newest_js_file('spec/javascripts/models/my_model')
#=> search for Dir['spec/javascripts/models/my_model*.{js,coffee}'] and return the newest file found
If you 100% know you won't need that support, modify your `Guardfile` as appropriate.