have u tried using pry to debug the issue?
Sent from my iPhone
On Apr 29, 2013, at 5:42 PM, Vighnesh Rege wrote:
> Hey guys,
>
> I was wondering if any of you knows the answer to this:
> http://stackoverflow.com/questions/16290365/start-ruby-debugger-if-rspec-test-fails
>
> Thanks!
>
> Vighn
ernel implements #test and stubs are done with
> method_missing.
> What's the recommended way to deal this this?
>
>
>
> --
> Un fleac... m-au ciuruit.
>
> ___
> rspec-users mailing list
> rspec-users@rubyforge.org
> ht
It would be better to split that into two tests that test when each error is
raised.
On Mar 9, 2013, at 4:24 PM, Adam Sroka wrote:
> It depends on what you really mean:
>
> 1) If you care that it is either OneError or OtherError, then these are two
> separate scenarios and should be written
Forgot to respond back. I was able to reset the factory girl sequence by
calling FactoryGirl.reload in a before callback and ditched the retry which
solved my problem.
Thanks
-S
On May 8, 2012, at 10:00 PM, David Chelimsky wrote:
> On Tue, May 8, 2012 at 12:55 PM, Samer Masry wrote:
&g
en
retried. Is that possible currently in rspec?
--
DryBlis - www.dryblis.com
Samer Masry | Rails Programmer
11 Ambler Ln, Emeryville, CA 94608
Tel.:510-991-7523 | Cel.: 714-814-8508
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyfo