Forum: RSpec Features failing to run correctly under 0.3.2

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
85d99e7678d8720f6e00ab0f60fe6ea9?d=identicon&s=25 Andrew Premdas (Guest)
on 2009-05-06 18:45
(Received via mailing list)
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

Many thanks

Andrew
0be0e4aa42aacd9a8a95c792de273ca7?d=identicon&s=25 Aslak Hellesøy (aslakhellesoy)
on 2009-05-06 20:09
(Received via mailing list)
> 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
>

I'll take a look at it. What Rails version are you on?

Aslak
0be0e4aa42aacd9a8a95c792de273ca7?d=identicon&s=25 Aslak Hellesøy (aslakhellesoy)
on 2009-05-06 20:24
(Received via mailing list)
On Wed, May 6, 2009 at 9:20 AM, Andrew Premdas <apremdas@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/tic...
85d99e7678d8720f6e00ab0f60fe6ea9?d=identicon&s=25 Andrew Premdas (Guest)
on 2009-05-07 07:14
(Received via mailing list)
2.2.2 at the moment.

2009/5/6 aslak hellesoy <aslak.hellesoy@gmail.com>
85d99e7678d8720f6e00ab0f60fe6ea9?d=identicon&s=25 Andrew Premdas (Guest)
on 2009-05-07 07:21
(Received via mailing list)
Thanks Aslak, I'll try this out when I get to work.

Andrew

2009/5/6 aslak hellesoy <aslak.hellesoy@gmail.com>
85d99e7678d8720f6e00ab0f60fe6ea9?d=identicon&s=25 Andrew Premdas (Guest)
on 2009-05-07 12:08
(Received via mailing list)
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@gmail.com>:
4e13e53b030e7751b777e439357fe902?d=identicon&s=25 Julian Leviston (Guest)
on 2009-05-07 12:36
(Received via mailing list)
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.
Cdf378de2284d8acf137122e541caa28?d=identicon&s=25 Matt Wynne (mattwynne)
on 2009-05-07 14:10
(Received via mailing list)
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
4e13e53b030e7751b777e439357fe902?d=identicon&s=25 Julian Leviston (Guest)
on 2009-05-07 15:39
(Received via mailing list)
Hi,

We're using Rails 2.3.2, and debugger doesn't seem to work in cucumber/
webrat running selenium mode. Has anyone else had this issue?

It seems to be skipping the debugger methods

Julian.
0be0e4aa42aacd9a8a95c792de273ca7?d=identicon&s=25 Aslak Hellesøy (aslakhellesoy)
on 2009-05-07 15:45
(Received via mailing list)
> Tried this out using your github repository. Can confirm this fixes
> our bug - looking forward to next gem release
>

Thanks for confirming Andrew

Aslak
3131fcea0a711e5ad89c8d49cc9253b4?d=identicon&s=25 Julian Leviston (Guest)
on 2009-05-07 19:31
(Received via mailing list)
On 07/05/2009, at 8:02 PM, Julian Leviston wrote:

> 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.
8f6f95c4bd64d5f10dfddfdcd03c19d6?d=identicon&s=25 Rick Denatale (rdenatale)
on 2009-05-07 21:30
(Received via mailing list)
On Thu, May 7, 2009 at 5:39 AM, Julian Leviston <julian@leviston.net>
wrote:
> Hi,
>
> We're using Rails 2.3.2, and debugger doesn't seem to work in
> cucumber/webrat running selenium mode. Has anyone else had this issue?
>
> It seems to be skipping the debugger methods

Rails noops the debugger method by default with a method which just
logs the call. If Kernel already has a debugger method then it
doesn't.

If you run script/server with the -u / --debugger option, then it
requires 'ruby-debug' and calls ::Debugger.start during
initialization.

Rails 2.3 does this by inserting a rack app which just does this.

David C. and I put support for the -u/--debugger options for the spec
command a few releases back, I don't know if this has any effect on
cucumber.



--
Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale
This topic is locked and can not be replied to.