[rspec-users] Helper methods starting with should_ get picked up as examples?

itentional behaviour by RSpec or some weird side effect? Cheers Peter Peter Marklund Garvar Lundins Gränd 7 11220 Stockholm Sweden Mobile Phone: +46-(0)70-4164857 Home Phone: +46-(0)8-50091315 Skype: peter_marklund IM: AIM - petermarklund, MSN - [EMAIL PROTECTED], Ya

Re: [rspec-users] Deprecating the mocking framework?

> 2) Chained stubs/expectations > > mock.stub!(:valid?).and_return(false) > mock.stub!(:valid?).and_return(true).after_receiving > (:save).and_return(true) On first look, that last line is pretty hard to read. I think I understand the intention now, but I'm not sure it harmonizes with the "Cl

Re: [rspec-users] testing behaviour or testing code?

> There's a very useful guideline in TDD that says "test YOUR code, not > everyone elses." The validation library we're testing here is > ActiveRecord's. It's already tested (we hope!). Personally, I don't have the courage to assume Rails code is always working. I know from experience it doesn't

Re: [rspec-users] Deprecating the mocking framework?

right now. (And newcomers still find it > impenetrable!) It looks like it's inevitable that it'll be broken up, > but, yeah, it's a real shame. > > Cheers, > -Tom > ___ > rspec-users mailing list > rspec-users@ruby

Re: [rspec-users] Setting use_transactional_fixtures=false for a single spec - a bad idea?

> I'd set up a separate folder for these specs and tweak the rake tasks > to run those specs in a separate process, w/ its own spec_helper that > sets config.use_transactional_fixtures to false. Thanks for the quick reply David! Sounds like your solution would be fairly easy to set up. For now t

[rspec-users] Setting use_transactional_fixtures=false for a single spec - a bad idea?

Hi! I would really like to find a way to allow me to write RSpec specifications for code that use database transactions. I know I can set config.use_transactional_fixtures = false in my spec_helper.rb. That works, and that's great, but it will (I think) slow down my specs quite a bit. I would

Re: [rspec-users] Canonical way to generate RSpec HTML report in Rails app

e task code: http://pastie.textmate.org/82520 > > Like a said, complete rip off of another builtin task. Notice that > it's executing as a dry-run, so it's not actually executing the > specs, just generating the report of what specs you have. Take that > out and it will act

[rspec-users] Canonical way to generate RSpec HTML report in Rails app

hanks! Peter Peter Marklund Garvar Lundins Gränd 7 11220 Stockholm Sweden Mobile Phone: +46-(0)70-4164857 Home Phone: +46-(0)8-50091315 Skype: peter_marklund IM: AIM - petermarklund, MSN - [EMAIL PROTECTED], Yahoo - peter_marklund2002 http://marklund