From: Sean DeNigris <sean@...>
Date: 2010-02-05T12:20:09+09:00
Subject: Re: Using Rspec for features and specs under Autotest

> Probably not a great idea to use mocks.  What real resources are slowing
> you down?
It's an application scripting library, so pretty much every method
call interacts with an application (mostly Apple events) - there are
windows popping up all over the place, lol.  I just want to use mocks
in the specs i.e. unit tests, and use real resources in the outer
cycle

> For the rest, if you use Cucumber for your acceptance tests (which you
> should!), then autotest will act as you described by default if
> AUTOFEATURE is true.
That's what I'm doing now.  What I was wondering was if anybody was
using rspec for the specs and rspec again for the features (instead of
cucumber).  Maybe by encapsulating the choice to use mocks or not as
the difference between the two cycles...

It seems like using Cucumber for the features when developers are the
users will obscure the usage, and I don't see the benefit to plain
English in this case.

Sean

Thanks for the reply!