Thanks, Pat.
-Corey
On Jan 25, 2008 12:22 AM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> No, the mock is set up to return nil when user= is called. Then he
> writes an example to actually expect the call to user=.
>
> Pat
>
> On Jan 23, 2008 8:02 AM, Corey Haines <[EMAIL PROTECTED]> wrote:
> > I g
I just discovered James Golick's resource_controller plugin
http://jamesgolick.com/resource_controller after spending another
stretch of boredom making the changes to nest yet another rails
resource controller. I'd actually slowed down this time to think
about what I was doing in hopes of automat
> 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 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
It seems to me that the RSpec bundle's 'it' snippet is in need of some
love. By default, a newly inserted spec passes. This seems odd as it
is misleading. It also makes it harder find what specs still need to
be completed if you return to an RSpec module after a break.
I propose that the 'i
Hi Matt,
one way of doing this is to leave the block out and just write:
it "should bla bla"
No 'do', no 'end'. The example will be pending this way.
François
Matt Darby schrieb:
> It seems to me that the RSpec bundle's 'it' snippet is in need of some
> love. By default, a newly inserted
On Jan 26, 2008 10:50 PM, Matt Darby <[EMAIL PROTECTED]> wrote:
> It seems to me that the RSpec bundle's 'it' snippet is in need of some love.
> By default, a newly inserted spec passes.
Not if you fill it out...and the BDD way is to write one example at a
time, not a complete spec beforehand.
>
