similar to: A better way to stub out constants

Hi Has anyone mocked a call like the following for backgroundrb? MiddleMan.new_worker(:class => :admin_email_worker, :args => params [:email]) I cannot seem to find the correct manner to do it. Would have liked to be able to do MiddleMan.should_receive (:new_worker).with(:class => :admin_email_worker, :args => {"body" => "my message"}) Cheers Shane

Hi I hope this is not OT. I''m training my replacement at work to do BDD Rails development. He''s done a CS/maths degree but has no professional programming experience, so he''s never NOT done a project without BDD. In a way I am jealous of his unspoilt situation :) I''ve gone about things this way: * first teach him some Ruby (he did mainly Java at

Hi In light of the fact that RSpec mocks are going into maintenance mode in the near future, I was wondering what everyone was switching to. I liked the look of FlexMock most, so gave that a shot. However, there''s a few things that don''t work well with RSpec due to the traditional differences in the way Test::Unit cases are written vs RSpec specs. (One spec per

Hi I can''t get heckle working. In fact, I''ve built an example so simple that it either shows a bug, or I am being really, REALLY stupid. Heckle does not appear to support RSpec directly, so I''m trying to use spec --heckle (RSpec trunk as of 10 mins ago, Heckle 1.4.1). I''ve constructed this pair of sample files: 18> ~/Desktop/heckle_test % cat

Hi I''m loading a gem on demand but can''t find a way to spec it. Assuming rubygems is already loaded, I assumed the following would work: describe SqliteConnection, " class" do it "should require ''sqlite3''" do Kernel.should_receive(:require).with("sqlite3") SqliteConnection.new end end Unfortunately

On Oct 31, 2007 11:36 AM, Scott Taylor <mailing_lists at railsnewbie.com> wrote: > When can we expect the next release of rspec? Definitely by the end of November. Likely by mid-November. Hopefully in a matter of days. The next release will be 1.1.0. We''re going to a release model in which 1.odd.x will be considered experimental. This means that while we will document

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 =

Hi all, The following only affects people who have bravely begun to experiment with the 2 day-old plain text story runner and definable groups of steps. For those who fit that bill, I just committed a few changes that will require you to make changes to your code. The StepMatchers class is now the StepGroup class. The step_matchers methods on PlainTextStoryRunner and StepGroup is now just

Hi Recently I sent a modified version of the GetBundle bundle to textmate-dev. It was failing because the RSpec bundle was from another repo (ie RubyForge). One of the replies said that the RSpec bundle was now in the MacroMates repo, which it is. Is that an officially handled thing? If so, what version of the RSpec bundle is being maintained there - CURRENT? It''s

Hi In a controller I have method that is accessed via an AJAX call and will conditionally do: render :nothing => true to test the condition hitting this line I was hoping to do something like: response.should render_template(:nothing) How should I test this behaviour? Cheers Shane

Is it possible to create a stub that returns hash values. For example I would like to convert this: @siteItem = stub(''plmSiteItem'', :one => "uno") To something like this: @siteItem = stub(''plmSiteItem'', {''one'' => ''uno'', ''two'' => ''dos''} ) So that I can do this:

Given the following ApplicationController specs: describe ApplicationController, "one facet", :shared => true do it ''foo'' ... it ''bar'' ... end describe ApplicationController, "some other facet", :shared => true do it ''abc'' ... it ''xyz'' ... end describe

Hey guys and gals, I have a snippet of code: Net::SMTP(@host, @port, @from_domain) do |smtp| @emails.each do |email| begin smtp.send_message email.encoded, email.from, email.destinations @emails_sent += 1 rescue Exception => e # blah end end end What I want to do is: Say there are 4 emails. First email is sent OK On the second email smtp raises a IOError

On Wed, Oct 14, 2009 at 5:49 PM, Scott Taylor <scott at railsnewbie.com> wrote: > > On Oct 14, 2009, at 3:36 PM, Joaquin Rivera Padron wrote: > > hello there, > how do you tipically spec private methods? The thing is ? have something > like this: > > def some_method > ?? complex_method + other_complex_methods > end > > private > def complex_method...

Hi Just something that I have been finding very helpful sometimes when I am stuck with "how could I test this?" moments is looking at the Rails test suite. At the moment I am working on testing our custom error_messages_for methods and I have found looking at how the Rails tests in active_record_helper work helpful :-) So just thought I''d share that. Have

Hi Was just using have_tag on an xml response and found the problem outlined and resolved here http://weblog.jamisbuck.org/2007/1/4/assert_xml_select Just wondered if there is any support in rspec? Cheers Shane Shane Mingins ELC Technologies (TM) PO Box 247 Santa Barbara, CA 93102 Phone: +64 4 568 6684 Mobile: +64 21 435 586 Email: smingins at elctech.com AIM: ShaneMingins Skype:

Hi I ran across the following when running spec on an old merb app. $ cat spec/spec.opts $ spec spec/models/topic_spec.rb Options written to spec/spec.opts. You can now use these options with: spec --options spec/spec.opts $ cat spec/spec.opts spec/models/topic_spec.rb $ spec spec/models/topic_spec.rb Options written to spec/spec.opts. You can now use these options with: spec --options

So in the past I''ve written a script that query''s a remote DB, takes the data, validates it, then does some processing, producing a new file with the data in a completely different format. Since this is a script with it''s own set of methods, etc, how do I go about testing the pieces parts? It seems like it should be no different than doing the rails testing I have

Hi We have specs in our rails project other than model/view/controller .. we have interests and lib ... using use_transactional_fixtures = true seems fine in a spec in the m/ v/c and interests directories but not in lib Just wondered if anyone had any quick thoughts as to why that may be??? Shane Mingins ELC Technologies (TM) 1921 State Street Santa Barbara, CA 93101 Phone: +64 4 568

Ok, this is INCREDIBLY finicky of me, and I''m a really finicky person at the best of times, but I noticed that when you use the TM Alternate File command to create specs, it does it with a header line like this: File.dirname(__FILE__) + ''/../../../spec_helper'' I use a header line like this require File.expand_path(File.join(File.dirname(__FILE__), *%w [..