Mark Trostler

this setup assumes the selenium server is running locally on port 4444 - is it?

Well the snipped you cut & pasted you did an 'npm config get jute:docRoot' instead of 'npm config set jute:docRoot' ??

ok cool - how about: % npm config set jute:docRoot .... -g % npm restart jute -g ?

Can you try that using a tag for the javascript instead of including it directly in the HTML? thanks, Mark

Unfortunately it is currently a requirement - I'm looking thru the code now to see how that can be avoided. The issue is the dynamic insertion of the JUTE code...

Thanks I am investigating. Mark On 9/13/11 10:28 AM, "Evan Culver" [email protected] wrote: > When trying to submit tests to Selenium 2.4.0, the hub fails to pass tests to >...

Ok I've just run JUTE successfully on Selenium Grid 1.0.8 with 2 remote controls and Selenium Standalone 2.6.0 so if there is an issue I'm not sure it's soda's fault...

BTW the way I test Selenium Grid is download the grid 1.0.8 from here: http://seleniumhq.org/download/ then start the hub like: % ant launch-hub and on same box: % ant launch-remote-control...

First - is there a Selenium grid running on 192.168.0.87 port 4444? Seems like JUTE is barfing because it cannot connect to your grid? Let me know, Mark On 9/12/11...

It has been tested against: selenium-server-standalone-2.4.0.jar, the older 1.0.3 RC server, and 1.0.8 of the grid stuff. It's not clear to me why JUTE would crash if it could not...