Hey guys,
I'm getting a weird error when trying to test something like the
following. It's a model that is using acts_as_attachment but the
weird thing is the equivalent Test::Unit case passes. Does anyone
have any ideas?
Best,
Dave
# it was a Test::Unit case first
def test_should_be
On Aug 15, 2007, at 7:57 AM, aslak hellesoy wrote:
> On 8/15/07, Scott Taylor <[EMAIL PROTECTED]> wrote:
>>
>> I've tried running Heckle with rspec on some of my classes, but keep
>> getting (what I believe to be) an infinite recursion. Is there some
>> way to supply extra options to heckle via.
Hi there,
I've been getting into RSpec recently and I must say what a fantastic
product I think it is. But, I've hit a bit of a problem. In my
ApplicationHelper I have a method which changes the view_paths in a
controller so a partial can be rendered from a different base
directory. It
What would be the best format for heckle options (through
> OptionParser) via the spec-command?
When we discussed this a few months back I proposed something like:
One alternative I thought of is to have a standard way to "promote" options
to other tools that spec invokes. Along the lines of:
On Aug 19, 2007, at 2:05 AM, Robert Feldt wrote:
>
>
> What would be the best format for heckle options (through
> OptionParser) via the spec-command?
>
> When we discussed this a few months back I proposed something like:
>
>
> One alternative I thought of is to have a standard way to "promote"
> > One alternative I thought of is to have a standard way to "promote"
> > options to other tools that spec invokes. Along the lines of:
> >
> > spec --heckle --options-heckle "--verbose --branches
> > MyModule::MyClass#my_method" ...
> >
> > and the argument to --options-heckle (or --options-rcov
