On Sun, Oct 2, 2011 at 11:57 AM, Felix Schäfer wrote:
>
> Am 01.10.2011 um 22:17 schrieb Justin Ko:
>
>> Specs do not over-ride each other
>
> That's what I was able to gather so far, unfortunately.
>
>> , so I can't think of an easy to do what you're trying to do. With that
>> said, I have never
I'm not sure what you mean by "core code" and "the user" here. Are you
writing an app, or a library, or a plugin? If you're writing an app, you
should test the app's behavior, which includes all the plugins and however
you configured them; if you're writing a library you should have scenarios
that
Am 01.10.2011 um 22:17 schrieb Justin Ko:
> Specs do not over-ride each other
That's what I was able to gather so far, unfortunately.
> , so I can't think of an easy to do what you're trying to do. With that said,
> I have never come across a situation like this because usually the app has
>
On Oct 1, 2011, at 7:03 AM, Felix Schäfer wrote:
> Hello,
>
> Is there some way to override a spec and more specifically parts of spec,
> ideally down to a specific example? I've been looking and googling for
> something like this, but I haven't found a good strategy for it.
>
> The use-case
Hello,
Is there some way to override a spec and more specifically parts of spec,
ideally down to a specific example? I've been looking and googling for
something like this, but I haven't found a good strategy for it.
The use-case is for a rails app that supports plugins, and those plugins may
