Last Updated: February 25, 2016
· fousa

Zeus makes Guard notifications go crazy

I have Guard setup in a Ruby on Rails application, and it works great. I can see my tests running from the moment I change something in my code.

I even get notifications in Mountain Lion's Notification Center, so it's awesome! But then I tried to integrate Zeus.


Here is an example of my Guardfile.

guard 'rspec', :version => 2, :cli => "--color --format nested --fail-fast", :test_unit => false do
  watch(%r{^lib/(.+)\.rb$}) { |m| "spec/lib/#{m[1]}_spec.rb" }
  watch('spec/spec_helper.rb') { "spec" }

  # Rails example
  watch(%r{^app/models/(.+)\.rb$}) { |m| "spec/models/#{m[1]}_spec.rb" }

Setup Zeus

And then I tried Zeus, you can checkout another #protip on how to install this. I added another parameter to the rspec guard.

guard 'rspec', :version => 2, :cli => "--color --format nested --fail-fast", :test_unit => false, :zeus => true do

And after starting the server the tests ran super fast.

So everything still okay. But then I noticed that I only get notifications when my file broke or I changed something in the Guardfile. So this was not okay.


Remove the :zeus => true parameter, because this seems to block the notification for some reason.

An issue has been created in order to fix this, so let's hope we'll get to use Zeus + Guard in the near future.