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

update readme

Browse Source
This commit is contained in:
John Bintz 2011-05-24 06:30:57 -04:00
parent b2d4c3c2ea
commit c5785e313e
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -6,6 +6,8 @@ Add running your Jasmine specs to your `Guardfile` via [`jasmine-headless-webkit
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
`gem install guard-jasmine-headless-webkit` and then `guard init jasmine-headless-webkit` in your project directory to get started.
## `guard` options ## `guard` options
* `:all_on_start => false` to not run everything, just like `guard-rspec` * `:all_on_start => false` to not run everything, just like `guard-rspec`
@ -20,3 +22,8 @@ file is a little more complicated. `newest_js_file` extends the Guard DSL to sea
If you 100% know you won't need that support, modify your `Guardfile` as appropriate. If you 100% know you won't need that support, modify your `Guardfile` as appropriate.
## ...and the `.jst` file search?
I use Backbone.js a lot, and I put my view templates in `app/views/*.jst` and mash them all together with Jammit for use in my apps. Feel free
to change that, it's your Guardfile after all.