Re: [rspec-users] Rails code reloading in RSpec test environment?

What's wrong with using spork? Works well for me. The issue I've found is rails loading everything. So the only 'simple fix' is the spork kind (ie process fork) Cheers, Jason On 23/11/2011, at 7:46 AM, Ash Moran wrote: > Hi > > I've worked on a couple of Rails 3 apps recently and the test feed

[rspec-users] RSpec and Rake

Guys, Just upgraded to rspec / rspec-rails 2.6 today and noticed that it pulled in rake 0.9.0 which was causing the rails 3.0.7 tasks to blowup. I've downgraded rake to 0.8.7. Are there any 'side-effects' that may impact the operation of rspec? Cheers, Jason

Re: [rspec-users] Ruby Debugger - not working in rspec?

heers, Jason On 4 March 2011 21:47, David Chelimsky wrote: > On Mar 3, 2011, at 11:44 PM, Jason Nah wrote: > > Howdy, > > I'm trying to get the ruby debugger to breakpoint at a specific line in > source. > > Here's what I did: > >- Added require &quo

[rspec-users] Ruby Debugger - not working in rspec?

Howdy, I'm trying to get the ruby debugger to breakpoint at a specific line in source. Here's what I did: - Added require "ruby-debug" in spec_helper.rb - Added gem dependency to Gemfile (gem "ruby-debug" - In the spec, added before do breakpoint; 0; end - Ran it with rspec spec/mode

[rspec-users] Rake generate - not generating spec files

Howdy, I'm running the following stack: - rails 3.0.4 - - rake (0.8.7) - rspec 2.5.0 - rspec-rails 2.5.0 I created the rails app, and I didn't tell rails to exclude the default Test mechanisms. I installed it using rails generate rspec:install When I type rake g model User I g

Re: [rspec-users] Named routes problem... more rails than rspec

Thanks for that... although the exception still bugs me... and digging through the router code in rails is mighty obtuse. I'm switching over to rspec mocks to get me over this... (was using mocha). One problem I ran into, I'm testing a mailer (+ view), and I'm trying to generate the email ONCE f

[rspec-users] Named routes problem... more rails than rspec

Howdy, I have emailed before about the inconsistencies I'm spotting when using named routes/resource, but I think I've narrowed down the issue. It would seem this has nothing to do with rspec per se, but more with how routing works with rails. If you have an object instance, that isn't saved and

[rspec-users] RSpec 2.4, named/restful routes falling apart...

Guys, This could be me, but I thought I'd check For some reason, when I spec controllers, I run into this problem (intermittently it would seem). Right now, I have a spec that fails predictably. I'm using * Rspec 2.4.0 * Rspec-rails 2.4.1 * Rails 3 * Mocha 0.9.10 I have the following defined in