similar to: Why has the --color gone from my life?

Hello. I have lost the coloured output in autotest after updating to rspec v1.1.4 I was already using the edge version and was ok then, before the last update. Anyone knows something about this? Thank you. -- Posted via http://www.ruby-forum.com/.

Hello, I have noticed that, since version 1.1.4, autotest/autospec does not run any of my specs. After getting a hint from http://b.logi.cx/2008/10/9/non-auto-spec, I dove a bit deeper into the code and found that spec is no longer being run by ruby. I monkey-patched Autotest::Rspec in my .autotest file so that spec is again executed (using code taken from version 1.1.4). autospec is now

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

Hey all, Just a heads up that the ZenTest-3.9.0 release is not compatible with RSpec-1.1.2. I thought I had a release ready to go, but differences between a preview release of ZenTest that I received and the actual release seem to have broken compatibility. We''ll get this resolved soon, but in the mean time please hold off on upgrading to ZenTest-3.9.0 if you''re using RSpec.

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

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

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

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

Hello all, I''m new to rSpec but after reading a couple of tutorials I''ve become enamored. Anyway, I am at minute 42 of the rSpec basics screencast ( peepcode.com) and I''m having the following error running autotest w/rSpec: D:\ruby\projects\forecaster>autotest loading autotest/rails_rspec c:\ruby\bin\ruby -rrubygems -e "require ''redgreen''"

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

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

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

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 =

I have had this problem for a while. autotest has never worked properly for me. I have tried different versions of rspec with different versions of ZenTest. I have tried it with .autotest files and without. When I run autotest from my rails app root, it says: loading autotest/rails_rspec and then it just sits there. If I look at the output from autotest -v, it is traversing the tree and it

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

People, I''m trying to run autotest on rails 2.3 I get a NoMethodError. Here is what I see: Sat Mar 21 20:47 /b/tmp/myfc23 maco$ Sat Mar 21 20:47 /b/tmp/myfc23 maco$ autotest loading autotest/rails_rspec ./vendor/plugins/rspec/lib/autotest/rspec.rb:24:in `initialize'': undefined method `failed_results_re='' for #<Autotest::RailsRspec:0x1205b88> (NoMethodError)

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!

I''m having trouble getting autotest to run "out of the box" with rspec. I''ve got a Leopard setup with Zentest 3.5.0, rspec on trunk, and rails 2.0PR. No ".autotest" file. There are a couple of issues: 1. Running ''autotest'' inititally yields a command not found for "spec --diff unified etc etc". This seems to be an old issue but

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

I can''t figure out how to build rspec-rails as a gem when just cloned from github... there isn''t any .gemspec file or rake task that does this. Any help? -- Posted via http://www.ruby-forum.com/.