Forum: RSpec Sinitra 0.9.1 Webrat 0.4.2 Cuc problem

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Andrew P. (Guest)
on 2009-03-04 07:19
(Received via mailing list)
Have created sample sinatra cucumber app as suggested on wiki. Tried
env.rb configurations from there and aslaks git repo. With this
of gems I get the following error doing basic cuc tests

 When I visit '/foo'                                       #
      PATH_INFO must start with / (Rack::Lint::LintError)



      ./features/step_definitions/general.rb:3:in `When /^I visit
      features/basic.feature:17:in `When I visit '/foo''

Afraid I can't expand on this as I can't getting debugging working with
and sinatra.

All best

Pat N. (Guest)
on 2009-03-04 08:23
(Received via mailing list)
For what it's worth, here's how I had to hack Webrat to get my Sinatra
app working properly:
Rob H. (Guest)
on 2009-03-04 11:45
(Received via mailing list)
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

I think the hacks Pat used are solely to do with getting selenium mode
Pat N. (Guest)
on 2009-03-04 16:11
(Received via mailing list)

Is your Sinatra app using the "classic" style? If so, I think it would
work without need for modification. If your app is a class that
inherits from Sinatra::Base, you're likely to see issues unless you
take the steps in the Gist.

Andrew P. (Guest)
on 2009-03-04 16:57
(Received via mailing list)
The app runs fine, its the cucumber tests that don't. If you can point
me to
your app I'll give it go here.

I'm using classic style (just started with Sinatra)

2009/3/4 Rob H. <removed_email_address@domain.invalid>
Andrew P. (Guest)
on 2009-03-04 17:13
(Received via mailing list)
Apologies - false alarm - problem was with my step-definition

all best


2009/3/4 Andrew P. <removed_email_address@domain.invalid>
This topic is locked and can not be replied to.