Those two lines will only start to come into play when you actually load fixtures. If you have no fixtures, it shouldn't matter what you set them to. Someone on the list should correct me if I'm wrong, but transactional fixtures typically reduce the time it takes to run specs.
<br><br>How many examples are you running? I've got a few apps now with several hundred examples, all of my model specs use fixtures and everything is quite fast for me now that non-model specs use mocks/stubs. For me, the longest part of running specs is loading the rails framework. To isolate that, just run script/console on the same app and see how long it takes.
<br><br><div><span class="gmail_quote">On 5/12/07, <b class="gmail_sendername">Scott Taylor</b> <<a href="mailto:mailing_lists@railsnewbie.com">mailing_lists@railsnewbie.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Is there someway to remove all fixture processing? Can I set the<br>following two lines in spec_helper.rb to remove all fixture processing ?<br><br> config.use_transactional_fixtures = false<br> config.use_instantiated_fixtures
= false<br><br>I was actually able to setup a sqlite in-memory database without a<br>problem, using topfunky's plugin.<br><br>Even with drb, mocks & stubs, and an in-memory database, and no<br>(used) fixtures, things seem to be quite slow. Maybe this is more of
<br>a reflection on my aged Mac than anything else...<br><br>I think the real bottleneck is occurring in rake. I'll have to<br>checkout a profiler.<br><br>Thanks,<br><br>Scott<br><br><br><br>On May 12, 2007, at 11:34 AM, Jeff Dean wrote:
<br><br>> Are you using mocks/stubs for the controllers and views? This has<br>> made the biggest difference in my specs. The other thing that's<br>> sped up my specs is making sure I'm only loading fixtures for the
<br>> specs that absolutely need it on the models.<br>><br>> But no - I've never used in-memory databases, so I can't help you<br>> there.<br>><br>> On 5/12/07, Scott Taylor < <a href="mailto:mailing_lists@railsnewbie.com">
mailing_lists@railsnewbie.com</a>> wrote:<br>> My specs are still taking to long to run in a rails app. Is anyone<br>> using an in-memory database to run their specs? Any pointers or tips?<br>><br>> Scott
<br>><br>> _______________________________________________<br>> rspec-users mailing list<br>> <a href="mailto:rspec-users@rubyforge.org">rspec-users@rubyforge.org</a><br>> <a href="http://rubyforge.org/mailman/listinfo/rspec-users">
http://rubyforge.org/mailman/listinfo/rspec-users</a><br>><br>> _______________________________________________<br>> rspec-users mailing list<br>> <a href="mailto:rspec-users@rubyforge.org">rspec-users@rubyforge.org
</a><br>> <a href="http://rubyforge.org/mailman/listinfo/rspec-users">http://rubyforge.org/mailman/listinfo/rspec-users</a><br><br>_______________________________________________<br>rspec-users mailing list<br><a href="mailto:rspec-users@rubyforge.org">
rspec-users@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/rspec-users">http://rubyforge.org/mailman/listinfo/rspec-users</a><br></blockquote></div><br>