Have you tried using should_receive instead of stub! ?
Sent from my iPhone
On 22-Jul-08, at 8:37 PM, Ry An <[EMAIL PROTECTED]> wrote:
Im having a hard time with a rspec controller test im writting, I need
to stub! the User.find call twice once to return the owning user and
once to return the v
In my application, we connect to 2 databases, so we make a lot of
specs to test this type of interaction. When I run individual model
specs using spec, or using rake spec SPEC=xxx, they run *fine*. When I
run rake spec:models, all the specs which connect to the 2nd database
fail on errors
On 7-Jul-08, at 12:25 PM, yitzhakbg wrote:
This might be a loaded question on this forum, but here goes:
Just had a discussion with a prospective employer, a Ruby On Rails
shop. His
reaction to BDD development on every project was skeptical, saying
something
like: "It depends on the projec
Someone on the list was just referencing Typo -
http://svn.typosphere.org/typo/trunk/spec/controllers/comments_controller_spec.rb
Doesn't look like they use stories, though.
On 4-Jul-08, at 4:29 AM, Olivier Dupuis wrote:
Hello,
Anyone knows of open source projects that uses RSpec and RSpec
On 19-Jun-08, at 9:10 AM, Kyle Hargraves wrote:
The typical cause of these infinite loops is that your test suite
updates some file in your project; autotest notices the change and
immediately starts again.
The solution is to simply add exceptions to your project's .autotest,
ignoring any files
On 23-May-08, at 4:48 PM, David Chelimsky wrote:
On May 23, 2008, at 4:35 PM, Lori M Olson wrote:
Can anyone (David?) shed some light on what exactly this warning is
complaining about? I started seeing it when I upgraded to Rails
2.1 RC1 and the latest RSpec from git.
I'm getting
why this is showing
up.
Pat
On 5/23/08, Pat Maddox <[EMAIL PROTECTED]> wrote:
It appears when you write a spec like
describe FooModule do ...
Pat
On 5/23/08, Lori M Olson <[EMAIL PROTECTED]> wrote:
Can anyone (David?) shed some light on what exactly this warning is
complaini
Can anyone (David?) shed some light on what exactly this warning is
complaining about? I started seeing it when I upgraded to Rails 2.1
RC1 and the latest RSpec from git.
I'm getting it in some helper specs that I'm writing. And yes, I am
including a module there, to reuse some utility me
