github-migration/guard-jasmine-headless-webkit
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Use Guard with jasmine-headless-webkit
7 Commits 3 Branches 10 Tags 117 KiB
Ruby 92.4%
Gherkin 5.9%
Shell 1.7%
b2d4c3c2ea
Go to file
John Bintz b2d4c3c2ea readme tweak
2011-05-24 06:22:01 -04:00
lib/guard yeah, it's working 2011-05-23 21:28:01 -04:00
spec yeah, it's working 2011-05-23 21:28:01 -04:00
.gitignore initial commit 2011-05-23 18:37:19 -04:00
Gemfile yeah, it's working 2011-05-23 21:28:01 -04:00
guard-jasmine-headless-webkit.gemspec tweak gemspec 2011-05-23 21:38:29 -04:00
Guardfile yeah, it's working 2011-05-23 21:28:01 -04:00
Rakefile initial commit 2011-05-23 18:37:19 -04:00
README.md readme tweak 2011-05-24 06:22:01 -04:00

README.md

Guard support for jasmine-headless-webkit

Add running your Jasmine specs to your Guardfile via jasmine-headless-webkit. Nice!

guard 'jasmine-headless-webkit' do
  watch(%r{^app/assets/javascripts/(.*)\..*}) { |m| newest_js_file("spec/javascripts/#{m[1]}") }
end

guard options

  • :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.