Will Sargent wrote:
>> I'd go one further than Pat Maddox's point: If your unit specs aren't
>> going to touch the database, then you really ought to be running a
>> tier of more integrated tests on your workstation before every checkin
>> (and again on the CI server). For obvious reasons, purely
> I'd go one further than Pat Maddox's point: If your unit specs aren't
> going to touch the database, then you really ought to be running a
> tier of more integrated tests on your workstation before every checkin
> (and again on the CI server). For obvious reasons, purely mock-based
> unit tests/
Will,
I wanted to do something similar. To avoid losing all the tasks and
other goodness Spec::Rails gives you for free, I just created a
separate top-level directory.
/spec
/models
/controllers
...
/unit
/models
...
(It bugs me not having it all contained in one directory, but it's
co
On Jan 23, 2008 12:12 AM, Will Sargent <[EMAIL PROTECTED]> wrote:
> Basically the Jay Fields style of testing -- I want the unit tests to
> be run all the time on a continuous integration server, but the
> integration/functional and system tests to be run only once a night.
I would suggest letting
David just posted about the new --patterns option in the trunk. His examples
don't include changing the directory structure, but I would think that it
would allow that. If not, that would be a good patch.
http://blog.davidchelimsky.net/articles/2008/01/20/rspec-new-pattern-option
-Corey
On Jan 2
I'd like to change the rspec directory structure from
/spec
/model
/controllers
etc
to
/spec
/unit
/models
/controllers
/lib
/functional
/models
/controllers
etc.
Basically the Jay Fields style of testing -- I want the unit tests to
be run all the time on
