Yeah, I figured out it was from upgrading test/unit. Remove the 2.X test/unit gem and you should be fine.
On Sun, Oct 4, 2009 at 6:55 AM, Paco Guzman <li...@ruby-forum.com> wrote: > David Chelimsky wrote: > > On Tue, Sep 29, 2009 at 9:37 PM, ignu <ignu.sm...@gmail.com> wrote: > >> � � � �from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in > >> active_support/dependencies.rb:158:in `require' > >> `gem_original_require' > >> � � � �from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in > >> `require' > >> � � � �from /Library/Ruby/Gems/1.8/gems/activesupport-2.3.4/lib/ > >> active_support/dependencies.rb:158:in `require' > >> � � � �from /Users/ignu/code/surveighor/spec/spec_helper.rb:6 > > > > What versions of rails, rspec and rspec-rails were you using > > successfully before you did this upgrade? Did you run "script/generate > > rspec"? Were you seeing test/unit output before the upgrade? > > I have the same problem > > I'm using > Rails 2.3.4 in vendor/rails > Rspec 1.2.8 > Rspec-Rails 1.2.7.1 > > I load the rspec libraries in the test.rb file > config.gem "rspec", :version => '1.2.8', :lib => 'spec' > config.gem "rspec-rails", :version => '1.2.7.1', :lib => false > > If I execute: "rake spec" in the console I got: > anything > If I execute: "RAILS_ENV=test rake spec" in the console I got: > Loaded suite /usr/local/bin/rake > Started > > > Finished in 0.000149 seconds. > > 0 tests, 0 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, > 0 notifications > > I added some puts commands in my user_spec.rb file and I've noticed that > the rspec "it" blocks aren't executed. > > Any idea what happens? > > Thanks > > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users
_______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
