rspec users - May 2009 - Features failing to run correctly under 0.3.2

Tried this out using your github repository. Can confirm this fixes
our bug - looking forward to next gem release

Thanks

Andrew

2009/5/7 Andrew Premdas <apremdas at gmail.com>:
> Thanks Aslak, I''ll try this out when I get to work.
>
> Andrew
>
> 2009/5/6 aslak hellesoy <aslak.hellesoy at gmail.com>
>>
>>
>> On Wed, May 6, 2009 at 9:20 AM, Andrew Premdas <apremdas at
gmail.com> wrote:
>>>
>>> Having significant problems getting an upto date environment with
>>> cucumber and rspec since 0.3.0. I have put the relevant files
including a
>>> backtrace ?in a gist?http://gist.github.com/107586. I''d
really appreciate it
>>> if someone could take a look at this.
>>> All these features ran fine using cuc 0.3.0 and rspec 1.2.2
>>
>> There is already a bug report for this:
>>
>>
>>
https://rspec.lighthouseapp.com/projects/16211/tickets/309-background-scenario-outline-before-hook-interaction
>>
>>>
>>> Many thanks
>>> Andrew

Hey all,

Has anyone else had any issues with trying to get APPLICATION code  
debugging when using cucumber, selenium & webrat?

I can debug steps just fine, but debugs in application code get  
skipped over under selenium for some reason.

Is this usual?

Julian.

On 07/05/2009, at 8:02 PM, Julian Leviston wrote:
> Hey all,
>
> Has anyone else had any issues with trying to get APPLICATION code  
> debugging when using cucumber, selenium & webrat?
>
> I can debug steps just fine, but debugs in application code get  
> skipped over under selenium for some reason.
>
> Is this usual?
>
> Julian.

Hi.

I realised that it was because I was simply running the server  
automatically - when I manually started it, I got access to the  
debugger server. All good.

Thanks

Julian.

On 7 May 2009, at 11:02, Julian Leviston wrote:
> Hey all,
>
> Has anyone else had any issues with trying to get APPLICATION code  
> debugging when using cucumber, selenium & webrat?
>
> I can debug steps just fine, but debugs in application code get  
> skipped over under selenium for some reason.
>
> Is this usual?
Well it''s out of process, so that might have something to do with it.

I don''t know how webrat starts the mongrel to serve pages to selenium,
but that''s where you''d need to look. I suggest you ask on the
webrat
mailing list about this.

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com