Thanks -- that confirms the results of our experiments.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
We're just running into it now, but we're using after_commit in Rails 3 for
the first time. The callback appears not to fire in our specs -- I noticed
your posting but have not had luck getting the gem to load. Bundler 1.0.7
requires the gem, and it generates this:
We haven't had the time to try to isolate the cause of the slowdown, but
whatever the cause, it seems to be widespread as I have seen others
reporting slowdowns of the same magnitude we have experienced. Our suite of
700 tests used to run in about 1 minute and on the same machine, with the
I've started a chart of differences between RSpec 1 and 2 here:
http://snyderscribbles.blogspot.com/2011/01/rspec-2-changes-from-rspec-1.html
I'll gladly post any new discoveries anyone want to contribute.
On Dec 4 2010, 3:22 pm, Jim Morris wolfma...@gmail.com wrote:
I am trying to upgrade a
Most of our RSpec2 conversion has been done since version 2.4, so my
report of performance 2-3 times slower than RSpec 1 is based on those
releases.
On Jan 13, 11:11 am, David Chelimsky dchelim...@gmail.com wrote:
On Jan 13, 2011, at 12:36 PM, Kurt wrote:
Hi -- Thanks for sharing all your
Hi -- Thanks for sharing all your tips. I couldn't understand your
line about what replaces have_text, however. I don't see a method
called matches or match...
I think your list might be the start of an effort by users to document
RSpec2 the hard way, since a lot has changed that the core team
Where are the changes to RSpec2 documented? I haven't been able to find a
list of changes that would include something like this removal of
have_text. Thanks.
___
rspec-users mailing list
rspec-users@rubyforge.org
In RSpec 1.x, a print statement in the spec would print out with the
results from that spec. In RSpec 2.x, the print statements are
separated from the spec results. Is there a way to restore the 1.x
behavior, so quick debugging work we do with print statements can
easily be associated with the
I just installed rspec-rails 2.3.1 gem into a new Rails 3.0.3 app, ran
the rspec:install generator, but the system doesn't see any other
RSpec generators (like rspec_controller), and the server will no
longer start.
Both report this error:
