On Tue, Dec 8, 2009 at 2:17 AM, Sam Woodard wrote:
> Code and tests at,
>
> http://gist.github.com/251480
The objects you're setting expectations on are not the same objects that are
being loaded by emailed_association_requests.to_send on line 4 of the gist.
They may have the same database IDs,
Thank you so much for your detailed reply. This really helped!
Sam
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
I would like to be able to write a custom matcher so that I could call
this test, for instance:
@user.should be_allowed_to_visit(url)
@non_welcome.should_not be_allowed_to_visit(url)
The matcher would call Webrat methods such as 'visit'.
The problem is that it would try to call 'visit' from Us
On Tue, Sep 29, 2009 at 9:37 PM, ignu wrote:
>
> So after I updated all my gems, I started getting:
>
> /Library/Ruby/Gems/1.8/gems/activesupport-2.3.4/lib/active_support/
> dependencies.rb:105:in `const_missing': uninitialized constant
> Test::Unit::TestResult::TestResultFailureSupport (NameErro
Matt,
I was facinated to read the email thread on Cuke's wire protoccol. You guys
collaborated well.
I have been working on my own to develop a similar protocol for RSpec. It is
totally external to RSpec right now and very primitive.
Whereas with Cucumber, the step definitions are run on some ot