Something in the latest iteration of spork, guard, or rspec now causes all examples to be run, not just tagged examples (say, with :focus => true). This was posted as an issue for rspec:
https://github.com/dchelimsky/rspec/issues/47 But when running the same command that guard generates in verbose mode: DEBUG (09:48:16): Command execution: bundle exec rspec --drb -f progress -r /Users/skaufman/.rvm/gems/ruby-1.9.3-p0@ee_core/gems/guard- rspec-0.6.0/lib/guard/rspec/formatters/notification_rspec.rb -f Guard::RSpec::Formatter::NotificationRSpec --out /dev/null --failure- exit-code 2 spec directly on the command line: $ bundle exec rspec --drb -f progress -r /Users/skaufman/.rvm/gems/ ruby-1.9.3-p0@ee_core/gems/guard-rspec-0.6.0/lib/guard/rspec/ formatters/notification_rspec.rb -f Guard::RSpec::Formatter::NotificationRSpec --out /dev/null --failure- exit-code 2 spec rspec does limit the run to tagged examples. So this doesn't appear to be an rspec issue per se. I've tried to poke in the guts of spork and guard looking for clues, but I'm clueless. Any ideas about which gem is at fault so that an issue can be filed in the right place at github and asked in the right Google group? Here's the configuration where this behavior occurs (with Rails 3.1.3): guard (0.10.0) guard-rspec (0.6.0) spork (0.9.0.rc9) guard-spork (0.5.1) rspec-core (2.8.0) rspec-expectations (2.8.0) rspec-mocks (2.8.0) rspec (2.8.0) rspec-rails (2.8.1) TIA. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
