On Thu, Dec 10, 2009 at 5:40 PM, Simon Stewart
<
simon.m...@gmail.com> wrote:
>
> We have the "selenium-server-standalone" target, which builds the
> standalone server, but it doesn't have all the testing stuff shoved
> into it.
>
Ah, got it. I'm seeing 403 forbidden messages when I try to use for
WebDriver though, with both the Java and the Ruby client:
org/openqa/selenium/remote/RemoteWebDriver.java:428:in
`throwIfResponseFailed': java.lang.RuntimeException: <html>
(NativeException)
<head>
<title>Error 403 Forbidden for Proxy</title>
</head>
<body>
<h2>HTTP ERROR: 403</h2><pre>Forbidden for Proxy</pre>
<p>RequestURI=/wd/hub/session</p>
<p><i><small><a href="
http://jetty.mortbay.org">Powered by
Jetty://</a></small></i></p>
Also, the test_remote target doesn't seem to test the WebDriver bits
(only Selenium), and I see NPEs from the server side (that is,
InProcessTestEnvironment) when I run test_remote_firefox_rb.
I'm looking into it, but could use some help.
Jari