Re: [rspec-users] reusable specs - almost there

On 8/4/07, David Green [EMAIL PROTECTED] wrote: I have a lot of controllers with virtually identical functionality for most actions. I've been using shared behaviours to DRY things up a bit, but I still have to create separate behaviours for each context before I can use the shared behaviours

Re: [rspec-users] reusable specs - almost there

I agree with David, I think this is too much magic. You'll often have more duplication in specs than you will in production code. That's not a bad thing though, because specs need to be explicit about the behavior being performed. Duplication doesn't lead to the same mistakes that it does in

[rspec-users] Stubbing Enumerable#each

I have a mock of an instance of a class which descends from Array: class ArrayDescendent Array; end #... in the specs... @descendent = mock ArrayDescendent How would I stub out ArrayDescendent#each, which is inherited from Array, to return multiple values successively? I could use

[rspec-users] pending w/ no string

Is there some reason that pending() *MUST* take an argument? Scott ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users