similar to: Autotest/RSpec 1.1.4/Rails 2.1 Infinite Loop?

This applies to anyone using rspec''s trunk from >= 3220 with ZenTest <= 3.7.2. Anyone else, feel free to move on.... The next release of ZenTest, coming soon, includes some changes that improve the relationship between Autotest, it''s subclasses (like those in rspec) and .autotest, the file that you can use to plug into autotest''s hooks to extend/modify

When I work with a .html.erb file, the autotest rspec on rails stuff doesn''t understand the file to map it to the right test. I wanted to submit a patch for this, but I''m unsure where the specs would be to update. I found the necessary mapping in rspec_autotest.rb, but I can''t find any specs anywhere. Help? I just need to have /app/views/coupon/index.html.erb to map to

Hi folks, I''m going through railstutorial.org and so I apologize if I''m hitting the wrong group here and would appreciate any appropriate redirection if necessary. I''ve set up Spork + Autotest as per Michael''s instructions in http://ruby.railstutorial.org/chapters/static-pages#sec:testing_tools Essentially by doing the following (using rvm & I''m

False Positives I just discovered how easy it was to create a false positive when I, trying my first RSpec test, did this: ob.should eql?(''foo'') instead of: ob.should eql(''foo'') or: ob.should == ''foo'' As far as I can see, this is roughly equivalent to: ob.should false Neither eql?(''foo'') nor false causes the spec

Hi, I keep facing problems with autotest, and I don''t know what''s happening in the background, is there anyway to know what''s happening while testing? Example: @user = User.new @user.email = "testcom" @user.errors.on(:email).should_not be_empty ...throws error failure - You have a nil object when you didn''t expect it! - You might have expected an

I am writing a controller admin/cities_controller.rb it inherits from AdminController, so it''s defined like class Admin::CitiesController > AdminController Whenever I save the controller file, autotest freaks out: uninitialized constant Admin::AdminController (NameError) I''m pretty used to just hitting CTRL-C to get autotest to re-load all the files, or flicking to

Trying to set up a Rails 3 project with RSpec and Autotest. I followed these steps exactly: http://gist.github.com/365816 But when I start up autotest, I get: $ autotest loading autotest/rails style: Rails instead of: $ autotest loading autotest/rails_rspec2 style: RailsRspec2 And autotest doesn''t seem to do anything. Any idea what''s happening? I''m using Ruby

I am having a weird error that I have not had before... I''m bouncing it off the list to see if anyone else has had it, or to give me some pointers about how to find it. Basically, AUTOTEST will run (RSpec mode), fine, then suddenly, will complain that RAILS_ROOT is undefined. Then I stop and restart it, with no code change... no problem. It happens on different specs where I use

Where should the specs go for code in the "lib" directory of a Rails app? I made a folder, "spec/lib/", for storing such specs, and RSpec automatically picks them up when run using "rake spec". Before I go ahead and patch rspec_on_rails/lib/autotest/ rails_rspec.rb so that autotest can monitor these specs I''d like to ask whether this is the

Hi, I just updated to the latest RSpec 1.1.3 + ZenTest 3.9.1. I also have rspec 1.1.3 installed as a gem When starting autotest with -v option, there is a lot of noise because autotest does not ignore the vendor folder, the migrations, etc ...: Dunno! vendor/plugins/acts_as_solr/solr/lib/jetty-util-6.1.3.jar Dunno!

Is it possible to specify that certain tables not be cleared on each example. I''ve inherited a project where a good amount of enumerated data is stored in the database (US States, statuses, about 15-20 tables worth. Over all, it''s a reasonable decision that leads to solid production code (acts_as_enumerated is good). This data is read-only and relatively static; any

Just ran svn up this morning, and got this (after running ./script/ generate rspec) escher: ./script/spec spec/models/item_spec.rb Finished in 8.0e-06 seconds 0 examples, 0 failures ./script/spec:4:in `run'': wrong number of arguments (3 for 1) (ArgumentError) from ./script/spec:4 Using rails 1.2.3, rspec trunk, on Mac OS X.4.9. Any ideas, or is this a bug in

Am I correct in remembering that autotest (with Test::Unit) would rerun all the tests if a subset of the tests passed? If so, shouldn''t this behaviour also be present in rspec''s autotest library? Scott

The Rails ApplicationController (app/controllers/application.rb) serves as an abstract superclass for all other controllers in a Rails application and is a good place to put methods and filters which you want all of your controllers to use. In my case I''m using it to provide methods such as "current_user" and "logged_in?" etc. By default, RSpec

Test First Development is great...But should you use it when you are adding classes/methods on to external library that doesn''t have an extensive test suite? I noticed that the rspec plugin for autotest has no specs. David Chemlinsky said something to the list a while back that has been stewing in my subconscious - that you develop software differently using Test First

I am working on my first Rails BDD project with extensive tests since starting out with Rails a few years ago. Running RSpec or Cucumber is really slow. I''m using Rails 3 and RSpec 2. To run one model spec with only 5 tests takes almost 1 minute! When it finishes it says it took only 0.9 seconds to run the actual test. So obviously it is loading the environment that takes so long. I just

Bleeding-edge story-writers, How are you structuring your specs? I am working on a new project and tried this: ./lib ./blah ./spec ./blah ./stories But it breaks autotest, so I moved stories parallel to lib and spec. Also what about suffixes? I have adopted "xyz_story_spec.rb", and "xyz.story" for the time being, with the line runner =

My autotest runs but when I make changes to a spec it doesn''t reload. I checked another application I was building that had 1.0.9 but it was reloading fine. How would I debug a problem such as autotest not reloading? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20070930/6be7160d/attachment.html

Hi guys, I''m trying to find some information on how to get autotest to run the rspec2 tests. I have my project setup so "rake spec" runs the specs properly, but autotest seems to ignore/don''t know that there are specs to test. I read on the rspec2 wiki that autotest integration is o be added eventually. Any ideas on how to achieve this? Thanks, Jeroen

Hi, When I start the "autotest" it gives me the following error...not sure what HOME path I have to set...all Ruby/Rails related components are in path! --- C:\>autotest -rails C:/Tools/InstantRails/ruby/lib/ruby/gems/1.8/gems/ZenTest-3.3.0/lib/autotest.rb:285:in `expand_path'': couldn''t find HOME environment -- expanding `~/.autotest'' (ArgumentError) ---