On Jul 26, 2010, at 3:44 pm, Wincent Colaiuta wrote:
> Personally I wouldn't do this. It makes it harder for anybody coming to your
> project to understand what's going on, because they see this "contract 'foo'
> do" construct and don't know what it is unless they dig into your
> spec_helper.
El 26/07/2010, a las 14:09, Ashley Moran escribió:
> The solution I'm playing with is to extract shared contract (ie shared
> example groups) that you can mix into a spec for a host class (eg User,
> Checklist) above to prove the feature (here collections) works, without
> reference to the impl
On Jul 26, 2010, at 8:55 am, Wincent Colaiuta wrote:
> Seems to me that including the same shared example group twice in the same
> "describe" block is a bit of an abuse, to be honest. I don't think it was
> ever really intended to be used in that way.
You're right, it clearly wasn't intended
El 26/07/2010, a las 09:31, Ashley Moran escribió:
> I'm back again, and still on a quest to tame shared example to do my bidding.
> This time what I'm wondering is... is there any way to format shared example
> specdoc description output with data passed in with #let, or otherwise? eg:
> How
Hi
I'm back again, and still on a quest to tame shared example to do my bidding.
This time what I'm wondering is... is there any way to format shared example
specdoc description output with data passed in with #let, or otherwise? eg:
How do I get "1" and "2" into either of the placeholders h
