similar to: Problems with RESTfully generated helpers

Hi all, For those of you checking out the Rails 2.0 preview release: RSpec-1.0.8 does not support Rails 2.0. Unfortunately, we''re in the middle of some big changes to the internals in trunk and won''t be in a position to do a release for another week or so. Therefore, if you are using the Rails 2.0 preview, you''ll need to use the RSpec trunk. Additionally, right now

What is the general opinion about fixtures versus mocking and stubbing in model specs? I heard from agile on IRC that they save the database testing for integration testing, but I also see that the caboose sample applicaiton uses fixtures. I also noticed that on the rspec site, it says "Ironically (for the traditional TDD''er) these are the only specs that we feel should actually

Hey guys, Does anyone have any wisdom to share on the subject of speccing Rails layouts? Most of it''s plain old view specs stuff, but are there sensible ways to verify things like the yield call? (Mocking doesn''t catch that) Thanks, Matt -- Matt Patterson | Design & Code <matt at reprocessed org> | http://www.reprocessed.org/

Hi guys I''m new to rspec and was wondering if there is a quick setup to get it to work with autotest, sans rails. Thanks -- Jim Freeze -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20070919/f7eecd9e/attachment.html

I''m running rspec and rspec on rails in svn external so I am running the latest version of the trunk. Recently the rake spec task started braking the continuous integration server because the rake aborted. I checked my local and it ran with the same behavior.. and all of the devs on my team are now experiencing the same problem. All the spec''s are passing, but the rake task is

What do you guys think of this: if someone calls should_receive outside of an "it" block, it warns you. before(:each) do @foo = Foo.new @foo.should_receive(:monkeys) end would warn you that you''re setting an expectation in the wrong place, and that "stub" is correct when setting up objects. Opinions? courtenay

Thanks, first, to everyone who''s asked and answered questions on this list, and to the creators of RSpec - it is all very helpful. I''ve searched the mailing list, and had a couple 2hr googling sessions that didn''t help me find an answer. I''ve run into a problem getting my first non-trivial view spec to run. I get an error when trying to generate a link_to()

1 def create 2 @user = User.new(params[:user]) 3 @user.save! 4 self.current_user = @user 5 redirect_to user_path(@user) 6 flash[:notice] = "Thanks for signing up!" 7 rescue ActiveRecord::RecordInvalid 8 render :action => ''new'' 9 end I can''t seem to properly spec this out. I am trying numerous things, the latest one is

This may have turned up in the RSS feeds of many of you already, but for those who haven''t seen it yet, looks intersting: <http://errtheblog.com/post/7708> > The main problem with fixtures, for me, has always been how unfun > they are. They literally suck the fun out of anything they?re > around. You throw them in your test/ directory, then suddenly > testing

Hi everyone! I have been working on idea for an application framework in ruby the wraps around the wx ruby gem. The goal is to make a framework that is as easy as rails create applications using concise and dry ruby code. We are in need of some experienced help! If you are interested checkout the project on ruby forge. Anvil.rubyforge.com and the irc channel is #rubyanvil on irc . My buck on irc

Hi everyone, I''m trying to test the shorthand way to push objects into an array. My controller looks like: current_user.foos << @foo and I keep getting an error like Mock ''foos'' received unexpected message :<< with <FooClass> does anyone have a good solution for this? I tried controller.send(:current_user).labels.stub!(:<<).and_return([]) and

Hi all, Recently a user of my editor (Hamr) reported that while using ruby 1.8.6 on windows, the close button would re-open the entire application once and quit. I heard that 1.8.6 has had problems with SOAP because it double posts. Is there something completely screwed up in 1.8.6 or did I make a programming error? :) -TIA

Hi I''ve added a page to the wiki to show some screenshots opf the wxRuby samples: http://wxruby.rubyforge.org/wiki/wiki.pl?ScreenShots I''d like to get some screenshots for OS X to add to this, if anyone could supply them please. It would be nice to show the minimal sample for all three platforms, plus perhaps some of the ones that aren''t included there. Also if

I am racking my brain over this, probably because I only know very simple mysql functions. Basically I''ve got a few tables, ex: Albums (id,name,band_id); Bands (id,name,label_id), and Label (id,name) I want to search through both album.name, band.name, and label.name throwing all results into a variable, with no redundant info. I think what I need to be doing is setting up some

Hi Something that''s gnawing at me... to avoid using the SQLite3 gem I''m stubbing it out like this: before(:each) do @database = mock("SQLite3 database") SQLite3 = Module.new SQLite3::Database = Class.new SQLite3::Database.stub!(:new).and_return(@database) end But then it keeps nagging me:

Hello All, There seems to have been a lot of interest in getting wxScintilla incorperated, and I think most of us who want it, want it so we can create an editor, so to avoid multiple projects comming out with the same goal (Not really that bad of a problem....), I''m going to kick start this, and ask that anyone interested in developing a Editor with wxRuby and wxScintilla, to send

I''m trying to write a story for a Rails app which involves using the attachment_fu plugin to upload images. After blunting my pick on this for a while, google found me this: http://www.ruby-forum.com/topic/134743#600831 So it seems that there''s a hole in Rails integration testing and multipart form posting. David offered to incorporate a patch to story runner at the end of the

rspec-rails version 1.2.9 has been released! * <http://rspec.info> * <http://rubyforge.org/projects/rspec> * <http://github.com/dchelimsky/rspec-rails> * <http://wiki.github.com/dchelimsky/rspec/rails> * <rspec-devel at rubyforge.org> Behaviour Driven Development for Ruby on Rails. Changes: ### Version 1.2.9 / 2009-10-05 * enhancements * added route_to and

Hello, Just decided to check whether I am doing something that makes sense or not. I was thinking about how cool would it be to re-use examples (just like we reuse story scenarios with GivenScenario). I was not sure if this possibility already exists in rspec (and, honestly, was lazy to check), so I have created this helper: def given_it(name) example_definition =

Hi there, I have this form code in a view: <%= start_form_tag :action => "listByArtist", :id => artist.id %> <p><b>List by Artist:</b> <select id="artist_id" name="artists[id]"> <%= options_from_collection_for_select(@artists, "id", "name") %> </select> <%= submit_tag "List"