cpan-selenium-rc-perl
cpan-selenium-rc-perl copied to clipboard
lukec
Test::WWW::Selenium: Selenium Server hangs immediately after fired up
A while ago I encountered a problem with opening a link between a Perl application and a Selenium Server. I opened an "Issue 5507" with the Selenium folks. I believe it clearly describes the issue and a (not entirely satisfactory) work around.
The interesting part is that this issue got the status "WorkingAsIntended"! And the kind folks pointed me to the relevant part of the documentation. To quote:
"Yes, it is expected behaviour. A binging should poll the started server until it reports its readyness, that is until /status request returns 200 OK, see [1]".
As far as I know, Test::WWW::Selenium and/or its dependents do not implement that advice, or do they?
Is this something that you would consider doing? (Myself, I am too much of a newbie to even attempt such an endeavor.)
Hello,
I don't work on this module anymore, sorry. If you work on a patch I would review it.
Best, Luke
On Mon, Aug 12, 2013 at 2:19 AM, Meir Guttman [email protected]:
A while ago I encountered a problem with opening a link between a Perl application and a Selenium Server. I opened an "Issue 5507"http://code.google.com/p/selenium/issues/detail?id=5507&thanks=5507&ts=1366137673with the Selenium folks. I believe it clearly describes the issue and a (not entirely satisfactory) work around.
The interesting part is that this issue got the status "WorkingAsIntended"! And the kind folks pointed me to the relevant part of the documentationhttps://code.google.com/p/selenium/wiki/JsonWireProtocol#/status. To quote:
"Yes, it is expected behaviour. A binging should poll the started server until it reports its readyness, that is until /status request returns 200 OK, see [1]".
As far as I know, Test::WWW::Selenium and/or its dependents do not implement that advice, or do they?
Is this something that you would consider doing? (Myself, I am too much of a newbie to even attempt such an endeavor.)
— Reply to this email directly or view it on GitHubhttps://github.com/lukec/cpan-selenium-rc-perl/issues/6 .
Dear Luke!
OK, I’ll try to modify what’s required to implement that protocol. But I am not experienced at producing a ‘diff’ file/patch (are these two one and the same?) and/or applying it. So I hope you could at least do it for me.
Regards, Meir
From: Luke Closs [mailto:[email protected]] Sent: יום ב 12 אוגוסט 2013 13:05 To: lukec/cpan-selenium-rc-perl Cc: Meir Guttman Subject: Re: [cpan-selenium-rc-perl] Test::WWW::Selenium: Selenium Server hangs immediately after fired up (#6)
Hello,
I don't work on this module anymore, sorry. If you work on a patch I would review it.
Best, Luke
On Mon, Aug 12, 2013 at 2:19 AM, Meir Guttman [email protected]:
A while ago I encountered a problem with opening a link between a Perl application and a Selenium Server. I opened an "Issue 5507"<http://code.google.com/p/selenium/issues/detail?id=5507 http://code.google.com/p/selenium/issues/detail?id=5507&thanks=5507&ts=1366137673 &thanks=5507&ts=1366137673>with the Selenium folks. I believe it clearly describes the issue and a (not entirely satisfactory) work around.
The interesting part is that this issue got the status "WorkingAsIntended"! And the kind folks pointed me to the relevant part of the documentationhttps://code.google.com/p/selenium/wiki/JsonWireProtocol#/status. To quote:
"Yes, it is expected behaviour. A binging should poll the started server until it reports its readyness, that is until /status request returns 200 OK, see [1]".
As far as I know, Test::WWW::Selenium and/or its dependents do not implement that advice, or do they?
Is this something that you would consider doing? (Myself, I am too much of a newbie to even attempt such an endeavor.)
— Reply to this email directly or view it on GitHubhttps://github.com/lukec/cpan-selenium-rc-perl/issues/6 .
— Reply to this email directly or view it on GitHub https://github.com/lukec/cpan-selenium-rc-perl/issues/6#issuecomment-22483531 . https://github.com/notifications/beacon/uYeBfUvpPXf2fV10sDaeFx_6VyXtoqiPRvlTlrCKPtqIs_M_29yL2Q3xawxa40-z.gif
No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.3392 / Virus Database: 3211/6570 - Release Date: 08/11/13