My application (the one on which the wiki example is based) still runs
just fine on 0.9.1, so I don't think it's related to the version
change.
I think the hacks Pat used are solely to do with getting selenium mode happy.
___
rspec-users mailing list
rsp
On Wed, Mar 4, 2009 at 4:30 AM, Andrew Premdas wrote:
> With Cuc and Rails I'd be able to debug step definitions by putting
> 'debugger' in the relevant step definition. With Sinatra configured as above
> this doesn't work. Any tips on making this work and/or explaining whats
> different/
Just us
> Because the longer you wait, the more your code will diverge from your
> teammates'. If you don't commit often you rob them of the opportunity
> to reduce merge hell.
Please note I did say commit, and not push, and I inferred from Matt
he meant commit and not push (although he has explained othe
On Tue, Feb 24, 2009 at 9:17 AM, Matt Wynne wrote:
> You can even use git commit --amend to commit on red (e.g at the end of the
> day) and then change that commit later.
While I think commit --amend is very useful, I'm not sure why you'd
bother to commit at the end of the day, knowing full well
On Thu, Mar 13, 2008 at 4:21 PM, James Deville <[EMAIL PROTECTED]> wrote:
> Google for some of the stuff about story runner. It was originally not
> plain text, that's just a convenience. There are some earlier
> tutorials on David's blog about just doing stories.
I couldn't see anything on Davi
Hi,
Having just played with getting my first plain text story working, I
like how it all fits together. It worked out nicely.
However, I don't feel our project needs to have stories as plain text,
in fact it's a slight hindrance for us. Is there any sensible
mechanism for doing integration testin
> BTW, Are the PeepCode rSpec tutorials worth buying?
Anything from PeepCode is worth buying imho, but the specifically, the
three rspec ones I have watched have been excellent.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/
David,
Thanks for looking at the problem.
> The trick here is that render :partial is NOT getting called on the
> controller - it's getting called on the template that is yielded to
> render :update.
I think I follow, still getting my head around that.
> Here's the way I would handle this: http
Hi,
I'm trying to spec a controller method which renders some rjs as part
of a render :update block. The problem I'm having is that stub_render
or expect_render don't seem to allow and_return to work.
The controller method does:
if @thing.save
render :update do
