Skip Menu |

This queue is for tickets about the Test-WWW-Selenium-Catalyst CPAN distribution.

Report information
The Basics
Id: 64980
Status: open
Priority: 0/
Queue: Test-WWW-Selenium-Catalyst

Owner: Nobody in particular
Requestors: mail [...]

Bug Information
Severity: Wishlist
Broken in: 0.06
Fixed in: (no value)


Subject: Why restrict server to localhost?
Download (untitled) / with headers
text/plain 334b
Sorry, forgot the subject line in my last post. Here's another suggestion: The server is currently started with $app->run($port, 'localhost'); But why restrict it to localhost only? By dropping the host argument, $app->run($port); the server will bind to all interfaces. This will allow for testing with remote Selenium servers.
Subject: test-www-selenium-catalyst2.patch
diff --git a/lib/Test/WWW/Selenium/ b/lib/Test/WWW/Selenium/ index 6da63e4..17f6742 100644 --- a/lib/Test/WWW/Selenium/ +++ b/lib/Test/WWW/Selenium/ @@ -217,7 +217,7 @@ sub start { exit 0; }; diag("Catalyst server running in $$") if $DEBUG; - $app->run($port, 'localhost'); + $app->run($port); exit 1; } $uri = 'http://localhost:' . $port;
Download (untitled) / with headers
text/plain 297b
I think that you'd need to compose the full URI to the app even if it wasn't started on localhost (to pass to the selenium server). I'd be happy to accept a patch to pass this in as an option, and a patch to make not binding to localhost as an option, but I'd not be happy doing that by default..

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to