similar to: ZenTest autotest now handles RSpec, yay!

Is anyone using rspec with autotest? Scott

Hi, I''ve been using the rspec and rspec_on_rails plugins quite happily on my Rails project for a while now. Today I noticed the autotest support in RSpec-1.0.3 and decided to give that a spin. Oh tragedy! $ autotest loading autotest/rails_rspec ./vendor/plugins/rspec_on_rails/lib/autotest/rails_rspec.rb:33:in `initialize'': undefined method `singularize''

Here is an example from autotest: class Autotest def self.run new.run end def new ... end def run ... end ... end How would I spec out Autotest.run? Two complications come to my mind: 1. How do I spec out class methods? (please point me to docs, if any. I can only find class level specing on "partial mocks" (of rails class objects) 2. How can I tell

Has anyone noticed any problems with the Rails story runner returning a response code of "0" when doing get/post/etc methods? I just grabbed the latest rails/rspec and just started noticing this problem, http://pastie.caboo.se/117497 Regular controller specs pass as expected. -- Josh Knowles phone: 509-979-1593 email: joshknowles at gmail.com web: http://joshknowles.com

Hi: This command: svn co svn://rubyforge.org/var/svn/rspec/tags/REL_0_9_0/rspec_on_rails/vendor/plugins/rspec_on_rail Gives me this output: svn: URL ''svn://rubyforge.org/var/svn/rspec/tags/REL_0_9_0/rspec_on_rails/vendor/plugins/rspec_on_rails'' doesn''t exist If I go the ''script/plugin install'' route, I get "Export complete." Anybody know

Fyi, I made the following renames: * RailsExample -> RailsExampleGroup * FunctionalExample -> FunctionalExampleGroup * ControllerExample -> ControllerExampleGroup * ViewExample -> ViewExampleGroup * HelperExample -> HelperExampleGroup * ModelExample -> ModelExampleGroup This was done to keep the naming consistent with ExampleGroup.

Is the rspec_autotest plugin mentioned here, http://blog.nicksieger.com/articles/2006/11/15/rspec-autotest-now-a-rails-plugin the accepted method of auto testing specs? It''s an old article, and after grabbing the plugin, and giving it a run, it fails with: $ rake spec:autotest:rails trunk/vendor/plugins/rspec_on_rails/lib/spec/rails/dsl/behaviour/rails_example.rb:31: undefined method

Hi! And now for the second part of the subject of my previous mails :) $ cat cucumber.yml default: . autotest: -v . autotest-all: -v -f progress . $ cucumber -i . -f progress PP Pending Scenarios: 1) enlightenment (meditation) $ AUTOFEATURE=true autospec # bug! prompt returns immediately, ZenTest gem not a dependency? a warning that autotest was not found would be nice. $ sudo gem

Hi, I''m new to rspec. I have some fixtures in /spec/fixtures. If they were in /test/fixtures they could be loaded with rake db:fixtures:load. Is there any way other than a symlink to load my rspec fixtures into the database with rake? Or, can I cause rspec to load the fixtures from /test/fixtures? Thanks, Paul

Hey, we''re currently using shoulda (http://dev.thoughtbot.com/ shoulda/) on a project and I saw some things that would be really nice to see in rspec, namely the should_ methods, and especially the should_be_restful method. Do these go against the rspec goals at all? Or could an ambitious programmer go to town implementing these for rspec_on_rails? Nathan Sutton fowlduck at

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

This is pretty much the same as last time around, if you recall. Thanks to Wilson for converting to the new form. I''ve added a few lines. Basically, it iterates over your model associations and does two things. - First, just try to call the association. Usually fixes speeling erors or other such silliness. - Second, try to find a record with an :include on the association. This

RSpec-1.1.3 has been released. If you''re using RSpec and autotest, you''ll have to upgrade to RSpec-1.1.3 and ZenTest-3.9.0 at the same time. == Version 1.1.3 Maintenance release. * Tightened up exceptions list in autotest/rails_spec. Closes #264. * Applied patch from Ryan Davis for ZenTest-3.9.0 compatibility * Applied patch from Kero to add step_upcoming to story listeners.

Hi all, Running on OSX 10.5.3, Latest Rspec trunk, Rspec rails trunk, latest autotest gem and rails 2.1 I''ve lost my colour output in autotest. rake spec gives colour output, but autotest gives me black and white. It was working a little bit before, I think I upgraded to the latest versions of everything to get all the textmate snippets talking and being friendly to one another again

Hi guys, I am having a problem with autospec. I upgraded to rspec-1.2.6, then I tried to run my specs with autospec. All my specs passes (green), until here, that''s all ok. The problem is that after all my specs have passed, the autospec stops, I mean, it doesn''t continue to run on background. The same behavior happened if one of my specs fails too. Is this the current default

Hey Guys. I just updated a project form 1.1.4 that was working with autotest 3.10 without issues: 1) Updated spec/model/project_spec.rb and it fired only that spec. 2) Updated app/model/project.rb and it fired only the matching spec file. After the update of rspec and rspec-rails as plugins a few minutes ago, it only run the controller specs and no other. Also, it doesn''t matter which

The "rspec" rake task collects all _spec files in the spec directory, and excludes the "watir" directory. Is this indicating a preference for using Watir over Selenium? I would like it better to standardize on something more neutral, ''ui'' perhaps? /Marcus -- Marcus Ahnve http://marcus.ahnve.net

All, Sorry for spamming this list about this but I think everyone who could help me with this problem is on this list... If there is a better place to post this question let me know. Anyways, I am trying to use rspec_on_rails_matchers in my rails app to improve my view specs but I can''t get them to work. The helpers for the form tags never seem to be called. I created a new Rails

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

autotest will no longer run my tests after I installed the rpsec gem and removed the plugins. I did install the rspec-rails gem as well. Is anyone else having this issue? -- Posted via http://www.ruby-forum.com/.