The setup for certain integration specs is a bit slow, and I'm generally
careful to make my 'it' blocks read-only. However, I also like to keep my
it blocks extremely focused on just 1 thing. This has become a performance
problem though, because the setup is executed for every 'it'. Is there
I have a simple module:
module Buyer
extend ActiveSupport::Concern
module ClassMethods
def delete_occasion(fb_id, recipient_fb_id, occasion_id)
# blah clah
end
end
end
I include it like this:
class User
include Buyer
end
this works when running the server, and in the conso
I'm trying to use:
get path_to_route
which had been working previously. Was this an intentional change? Can I
get this behavior back, or was there a reason it was removed.
Thanks all.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://ruby
I just did a bundle update, and my integration specs stopped working. I was
on Rails 3.0.5, and am now on 3.0.6. Any suggestions on how to get access to
those routes back? In case the subject wasn't clear, this is what is no
longer working:
get sessions_path
sessions_path (and every other pa
I'm using ree via rvm. Everything was just installed.
In autotest, the tests won't even start to run. When I run rspec
spec, the tests will run, but will crash at some point here:
src/tcmalloc.cc:390] Attempt to free invalid pointer: 0x10022d9a0
I'm not really sure where to look. Any recommend
am, David Chelimsky wrote:
> On Jan 21, 2011, at 10:32 AM, JDeville wrote:
>
> > I'd like to be able to test w/ this methodology, and i'm having
> > trouble figuring out where to hook in to rspec to do it. Near as I
> > can tell, the flow is this:
>
> >
Scott, check out Bourne. It's an add on to mocha that gives you
spies. I'm using it, and like it a lot.
On Dec 2 2010, 8:53 am, David Chelimsky wrote:
> On Dec 2, 2010, at 1:44 AM, Scott Bellware wrote:
>
> > I've tried three test spy mocking frameworks for RSpec that I know of.
> > Presently,
I'd like to be able to test w/ this methodology, and i'm having
trouble figuring out where to hook in to rspec to do it. Near as I
can tell, the flow is this:
run all of the before filters in the order of highest to lowest
context
<<-- I need to run something right here
run tests
run all of t
Problem ---
When I run autotest against my rails 3 app, I get some errors that
seem to imply that my @ variables are not be cleared for each
context. It happens only in my controller tests, but that may simply
be a coincidence. When autotest t