Autotest is running continuously - even when the files mtimes aren''t changing. I believe this only happens if using a failures file. autotest -v gives me: euclid% autotest -v loading autotest/rails_rspec /opt/local/bin/ruby -S script/spec -O spec/spec.opts spec/ controllers/log_entries_controller_spec.rb spec/views/login/ new_spec.rb spec/controllers/login_controller_spec.rb spec/models/ user_spec.rb spec/views/log_entries/edit_html.erb_spec.rb spec/views/ log_entries/index_html.erb_spec.rb spec/views/log_entries/ new_html.erb_spec.rb spec/views/log_entries/show_html.erb_spec.rb spec/helpers/login_helper_spec.rb spec/models/log_entry_spec.rb ........................................................................ .....F.. 1) ''LoginController routes should route create to POST /login'' FAILED expected "/login", got "/login/create" (using ==) ./spec/controllers/login_controller_spec.rb:13: script/spec:4: Finished in 3.04389 seconds 80 examples, 1 failure [["spec/previous_failures.txt", Fri Jun 08 01:13:32 -0400 2007]] (The last line is the important one). Is there a way to get around this via autotest? Or does this suggest that Autotest::Rspec needs to be patched? Or should rspec use a standard failures file? Scott
El 8/6/2007, a las 7:57, Scott Taylor escribi?:> Autotest is running continuously - even when the files mtimes aren''t > changing. I believe this only happens if using a failures file.Have you removed these lines from your spec/spec.opts file (no longer necessary)? --format failing_examples:previous_failures.txt --example previous_failures.txt Are you running the latest RSpec (contains some autotest-related fixes)? Cheers, Wincent
On Jun 8, 2007, at 4:01 AM, Wincent Colaiuta wrote:> El 8/6/2007, a las 7:57, Scott Taylor escribi?: > >> Autotest is running continuously - even when the files mtimes aren''t >> changing. I believe this only happens if using a failures file. > > Have you removed these lines from your spec/spec.opts file (no longer > necessary)? > > --format > failing_examples:previous_failures.txt > --example > previous_failures.txt >In what revision did that change?! Is this applicable only to rspec_on_rails, or to rspec generally?> Are you running the latest RSpec (contains some autotest-related > fixes)?yep. trunk. It works. Thanks alot. Scott
El 8/6/2007, a las 14:09, Scott Taylor escribi?:> On Jun 8, 2007, at 4:01 AM, Wincent Colaiuta wrote: > >> Have you removed these lines from your spec/spec.opts file (no longer >> necessary)? >> >> --format >> failing_examples:previous_failures.txt >> --example >> previous_failures.txt > > In what revision did that change?! Is this applicable only to > rspec_on_rails, or to rspec generally?I don''t remember which exact revision, but I was seeing the exact same problem until David set me straight in this post <http:// rubyforge.org/pipermail/rspec-users/2007-May/001650.html>:> These lines configure rspec to limit the number of files that get run > when there are failures, but autotest is doing the same thing so there > is no need.I believe that file is specific to rspec_on_rails, in any case. For the record, when working in a Rails app, each time you do arspec/ rspec_on_rails plugin update I think you should probably run "script/ generate rspec" from the top level of your app; if it tells you that spec/spec.opts has been modified then you can hit the "d" key to see a diff of exactly what''s changed... In one of the recent RSpec updates, they dropped those lines from spec/spec.opts. Cheers, Wincent
On Jun 8, 2007, at 8:48 AM, Wincent Colaiuta wrote:> El 8/6/2007, a las 14:09, Scott Taylor escribi?: > >> On Jun 8, 2007, at 4:01 AM, Wincent Colaiuta wrote: >> >>> Have you removed these lines from your spec/spec.opts file (no >>> longer >>> necessary)? >>> >>> --format >>> failing_examples:previous_failures.txt >>> --example >>> previous_failures.txt >> >> In what revision did that change?! Is this applicable only to >> rspec_on_rails, or to rspec generally? > > I don''t remember which exact revision, but I was seeing the exact > same problem until David set me straight in this post <http:// > rubyforge.org/pipermail/rspec-users/2007-May/001650.html>: > >> These lines configure rspec to limit the number of files that get run >> when there are failures, but autotest is doing the same thing so >> there >> is no need. > > I believe that file is specific to rspec_on_rails, in any case. > > For the record, when working in a Rails app, each time you do arspec/ > rspec_on_rails plugin update I think you should probably run "script/ > generate rspec" from the top level of your app; if it tells you that > spec/spec.opts has been modified then you can hit the "d" key to see > a diff of exactly what''s changed... In one of the recent RSpec > updates, they dropped those lines from spec/spec.opts.Ah - that diff is very helpful. I had no idea. Thanks, Scott
On 6/8/07, Scott Taylor <mailing_lists at railsnewbie.com> wrote:> > On Jun 8, 2007, at 8:48 AM, Wincent Colaiuta wrote: > > > El 8/6/2007, a las 14:09, Scott Taylor escribi?: > > > >> On Jun 8, 2007, at 4:01 AM, Wincent Colaiuta wrote: > >> > >>> Have you removed these lines from your spec/spec.opts file (no > >>> longer > >>> necessary)? > >>> > >>> --format > >>> failing_examples:previous_failures.txt > >>> --example > >>> previous_failures.txt > >> > >> In what revision did that change?! Is this applicable only to > >> rspec_on_rails, or to rspec generally? > > > > I don''t remember which exact revision, but I was seeing the exact > > same problem until David set me straight in this post <http:// > > rubyforge.org/pipermail/rspec-users/2007-May/001650.html>: > > > >> These lines configure rspec to limit the number of files that get run > >> when there are failures, but autotest is doing the same thing so > >> there > >> is no need. > > > > I believe that file is specific to rspec_on_rails, in any case. > > > > For the record, when working in a Rails app, each time you do arspec/ > > rspec_on_rails plugin update I think you should probably run "script/ > > generate rspec" from the top level of your app; if it tells you that > > spec/spec.opts has been modified then you can hit the "d" key to see > > a diff of exactly what''s changed... In one of the recent RSpec > > updates, they dropped those lines from spec/spec.opts. > > Ah - that diff is very helpful. I had no idea.I did blog about it a while back: http://blog.davidchelimsky.net/articles/2007/05/29/rspec-and-autotest I''ll also add it to the upgrade page http://rspec.rubyforge.org/upgrade.html> > Thanks, > > Scott > > _______________________________________________ > rspec-users mailing list > rspec-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users >