[rspec-devel] closing in on rspec story runner (rbehave)

David Chelimsky dchelimsky at gmail.com
Tue Aug 7 12:52:57 EDT 2007


On 8/7/07, Scott Taylor <mailing_lists at railsnewbie.com> wrote:
>
> On Aug 7, 2007, at 1:08 AM, David Chelimsky wrote:
>
> Which branch are you working on?

rbehave-import

> It didn't look like you had resolved it, as of a few hours ago.

cd branches/rbehave-import/rspec
rake

That gives me all passing specs w/ 99.6% coverage.

> On another note: how do you use autotest with rspec's development?

Sadly, I don't. Haven't solved that problem yet.

> Autotest always wants to use the gem, not the rspec in the local
> rspec/rspec/bin dir.  If you don't use autotest, then how do you use
> the --failures and --examples?  The default rake spec task doesn't
> seem to use the --failures
>
> Scott
>
>
> > I resolved the two failures Dan spoke of in another thread and am
> > close to getting to 100% coverage. If someone wants to look at that it
> > would be helpful. It involves objects that are generated while
> > bootstrapping the runner, so it'll probably need to be refactored a
> > bit in order to get access to those elements in specs.
> >
> > Getting close.
> >
> > Cheers,
> > David
> > _______________________________________________
> > rspec-devel mailing list
> > rspec-devel at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-devel
>
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>


More information about the rspec-devel mailing list