Instructions for setting up selenium

[gprasant]

OS: OS X 10.8.5
node : v0.10.26
testium: v1.7.0
chrome: v35.0.1916.153

---

I tried to setup testium from the project homepage. When I try to run a basic testium CLI instance, I get an error saying that selenium.jar is not valid. Here's a command log :

➜  tmp  ./node_modules/.bin/testium

/Users/pguruprasad/tmp/node_modules/testium/lib/cli/console.js:70
        throw error;
              ^
Error: Process "selenium" crashed. See log at: /Users/pguruprasad/tmp/node_modules/testium/lib/cli/../../log/selenium.log.
    at procError (/Users/pguruprasad/tmp/node_modules/testium/lib/selenium/process/port.js:47:13)
    at /Users/pguruprasad/tmp/node_modules/testium/lib/selenium/process/port.js:64:19
    at Socket.<anonymous> (/Users/pguruprasad/tmp/node_modules/testium/node_modules/portscanner/lib/portscanner.js:81:5)
    at Socket.EventEmitter.emit (events.js:95:17)
    at TCP.close (net.js:465:12)
➜  tmp  cat /Users/pguruprasad/tmp/node_modules/testium/lib/cli/../../log/selenium.log
[SERVICE] 13:11:24.718 - Starting selenium
[SERVICE] 13:11:24.725 - waiting for selenium to listen on port 4444
Error: Invalid or corrupt jarfile /Users/pguruprasad/tmp/node_modules/testium/bin/selenium.jar

Can you please provide instructions to setup up a working instance of selenium because the instructions provided on this project's repo dont seem to make a correct installation of selenium.

I also made sure that I am using the latest selenium server and selenium chrome driver :

➜  tmp  ./node_modules/.bin/testium --update-selenium
[testium] grabbing selenium standalone server 2.41.0
[testium] grabbing selenium chromedriver 2.9

[EndangeredMassa]

There are no other instructions. Testium should do everything for you.

Selenium crashed. The error message mentions a log at /Users/pguruprasad/tmp/node_modules/testium/lib/cli/../../log/selenium.log. An actual error message should be in there somewhere. Can you make a gist of the full log and link it here?

[gprasant]

My above desc includes a cat of the selenium.log. The only thing I can find there is that selenium.jar file is invalid (thats the full log . Theres only 3 lines in there )

[EndangeredMassa]

Oh, right. I was expecting to see a lot.

There is an issue with previous versions of testium that can pollute updated versions. Try rm -rf /tmp/testium, ./node_modules/testium/bin, then re-run testium tests.

[gprasant]

I did

$ rm -rf ~/.npm/testium   #nuke all older versions of testium
$ cd ~/tmp   # folder from where Im trying out stuff 
$ npm install testium 
$ npm ls testium
/Users/pguruprasad/tmp
└── testium@1.7.0 

I still get the same errors when I try to run the interactive testium console, and the same logs as before.

➜  tmp  cat /Users/pguruprasad/tmp/node_modules/testium/lib/cli/../../log/selenium.log
[SERVICE] 18:59:40.226 - Starting selenium
[SERVICE] 18:59:40.233 - waiting for selenium to listen on port 4444
Error: Unable to access jarfile /Users/pguruprasad/tmp/node_modules/testium/bin/selenium.jar

(can we talk about this on chat/irc)

[EndangeredMassa]

sure thing!

[EndangeredMassa]

Related PR: #87

[gprasant]

Thanks .