functionality provided in the protected methods. Again, the fact that
they have been specing the protected methods is an indication that
another object may want to be born to handle the extra
responsibility...
+1. The desire to unit test private methods always rings the
'refactor: extract c
Tim Haines wrote:
> Hi David,
>
> You were spot on. The generated authenticated_system_spec included
> AuthenticatedSystem. If I include AuthenticatedSystem into the
> SessionsController spec, then the specs all pass. This is a problem
> with the standard specs that resful_authentication builds
Actually, it was patched in June. The patch author chose to use .send.
http://github.com/technoweenie/restful-authentication/commit/8307820bee893b2ebbbf990b947a878ebe8b7624
Cheers,
Tim.
On Tue, Sep 2, 2008 at 3:15 PM, David Chelimsky <[EMAIL PROTECTED]>wrote:
> On Mon, Sep 1, 2008 at 6:22 PM,
Hi David,
You were spot on. The generated authenticated_system_spec included
AuthenticatedSystem. If I include AuthenticatedSystem into the
SessionsController spec, then the specs all pass. This is a problem with
the standard specs that resful_authentication builds for you - so I'll
looking at
On Mon, Sep 1, 2008 at 6:22 PM, Tim Haines <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I've noticed something a little odd with the session_controller specs that
> are generated from the rails plugin restful_authentication. When they're
> run with all the other app specs (i.e. when I first fire up
Actually, webrat already has a method for this. It will even modify the
CSS and image's paths to work correctly.. In your step simply type:
save_and_open_page
-Ben
Jonathan Linowes wrote:
> thanks
> perhaps a bit hackery, I've added this to my shared steps file:
>
> Given "(show me)" do
>
thanks
perhaps a bit hackery, I've added this to my shared steps file:
Given "(show me)" do
show_me
end
When "(show me)" do
show_me
end
Then "(show me)" do
show_me
end
and to my helper.rb
def show_me
File.open(RAILS_ROOT + "/public/dbug.html", "w"){ |f| f.puts
respon
Hi there,
I've noticed something a little odd with the session_controller specs that
are generated from the rails plugin restful_authentication. When they're
run with all the other app specs (i.e. when I first fire up autospec) the
specs all pass. However, if I touch the session_controller_spec
On 1 Sep 2008, at 21:30, aslak hellesoy wrote:
cucumber --help
Example:
cucumber path/to/file.feature --line 33
Or with Rake:
rake features FEATURE=path/to/file.feature CUCUMBER_OPTS="--line 33"
It's not documented on the Wiki yet. Pass the line number of one of
the steps. I think it's broke
On 1 Sep 2008, at 21:34, aslak hellesoy wrote:
On Mon, Sep 1, 2008 at 7:12 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
I'm hardly a story-runner expert, so I may be making a dumb
mistake here...
The scenario "Admin user merges two venues" fails with this ugly
backtrace:
rake aborted!
Comman
On Mon, Sep 1, 2008 at 3:31 PM, aslak hellesoy <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 1, 2008 at 9:25 PM, Priit Tamboom <[EMAIL PROTECTED]> wrote:
>> Hi!
>>
>> I'm new to Cucumber/Story Runner, but not so new to Rspec in general.
>> I googled a lot before
>> posting :-)
>>
>> I would like to mock
On Mon, Sep 1, 2008 at 7:12 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
> I'm hardly a story-runner expert, so I may be making a dumb mistake here...
> I'm trying to get one scenario to run another as part of its Given clause.
> It looks like this:
> Scenario: Admin user merges two venues
> GivenScen
On Mon, Sep 1, 2008 at 3:30 PM, aslak hellesoy <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 1, 2008 at 9:45 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
>> On Mon, Sep 1, 2008 at 12:08 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
>>> Am taking cucumber for a first spin today - first impressions are good
On Mon, Sep 1, 2008 at 9:25 PM, Priit Tamboom <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I'm new to Cucumber/Story Runner, but not so new to Rspec in general.
> I googled a lot before
> posting :-)
>
> I would like to mock openid consumer however I'm running out of ideas
> how to access session.
> I know
On Mon, Sep 1, 2008 at 9:45 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 1, 2008 at 12:08 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
>> Am taking cucumber for a first spin today - first impressions are good.
>> How do I go about running a single feature or scenario so I don't have to
On Mon, Sep 1, 2008 at 12:08 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
> Am taking cucumber for a first spin today - first impressions are good.
> How do I go about running a single feature or scenario so I don't have to
> run the whole lot when I'm working on a particular one?
There's no support
Hi!
I'm new to Cucumber/Story Runner, but not so new to Rspec in general.
I googled a lot before
posting :-)
I would like to mock openid consumer however I'm running out of ideas
how to access session.
I know I should avoid mocking in integration testing, but in this case
it makes sense.
Perhaps
In the past I've done this...
File.open(RAILS_ROOT + "/public/duh.html", "w"){ |f| f.puts response.body }
And then in terminal I go to my project root and type "open
public/duh.html". Although you may be able to get away with doing this
in your debugging session:
system "open #{RAILS_ROOT}
On 2008-08-30, at 12:35, Mark Wilden wrote:
On Sat, Aug 30, 2008 at 8:33 AM, Zach Dennis <[EMAIL PROTECTED]>
wrote:
On Fri, Aug 29, 2008 at 11:05 PM, Scott Taylor
> This isn't ruby - if you want ruby to include it, you'll need a
require
> statement (or a load, or autoload).
I think Scott me
Given I am running an rspec story
And it uses webrat
And I am using rdebug
When I am at a breakpoint (eg after a 'visits' in a step)
Then how can I open the current response in a browser to see what the
page actually looks like at that point?
___
I'm hardly a story-runner expert, so I may be making a dumb mistake
here... I'm trying to get one scenario to run another as part of its
Given clause. It looks like this:
Scenario: Admin user merges two venues
GivenScenario Admin user views two venues
W
Am taking cucumber for a first spin today - first impressions are good.
How do I go about running a single feature or scenario so I don't
have to run the whole lot when I'm working on a particular one?
cheers,
Matt
http://blog.mattwynne.net
http://songkick.com
In case you wondered: The
I find pronouncing the R with a piratey 'ar spec' helps avoid any
arse or peck embarrassment.
I'm still struggling with how to pronounce rspec in Japanese.
The best I've managed is 'l spec'
All these darn r's :)
--
Joseph Wilk
http://www.joesniff.co.uk
Matt Wynne wrote:
> On 30 Aug 2008, at
23 matches
Mail list logo
