testingbot / node-seleniumgrid Goto Github PK

Selenium Hub/Grid built in nodeJS and used in production on TestingBot.com

License: Apache License 2.0

JavaScript 99.97% Shell 0.03%

node-seleniumgrid's Introduction

node-seleniumgrid

Selenium Hub/Grid built in nodeJS and used in production on TestingBot.com.

At TestingBot we've been using this code for 11 months now, running on a single CPU server with the latest version of nodejs.

We built this to replace the Selenium grid functionality that comes with the default Selenium source code in Java. One of the reasons we used nodeJS was because we wanted it to be easy to read and understand.

With this code, you can run a Selenium grid, point your own Selenium nodes to it and run tests against it. It also comes with an option to use the TestingBot grid if a specific browser is not present on your grid. So for example: you have 2 virtual machines with both Linux and Windows but you also want to run tests against Mac. By using this grid, your tests will run on your own 2 virtual machines and use the TestingBot grid to run the tests on our Mac VMs.

Requirements

General:

NodeJS, at least v0.10.0
npm

User Quick Start

sudo npm -g install node-seleniumgrid
node-seleniumgrid -k testingbot_key -s testingbot_secret

You now have a local Selenium grid running on port 4444. Start a Selenium node and point it to this grid, it should register to the grid. Now run a simple Selenium test against your new grid, depending on the capabilities you requested it should forward the test to your Selenium node.

run node-seleniumgrid
start a node java -jar selenium-standalone.jar -role node -hub http://my-computer-ip:4444/grid/register
point your test to run on my-computer-ip port 4444:

require "rubygems"
require "selenium-webdriver" 
require "selenium/client"

caps = {
  :browserName => "firefox",
  :version => "22",
  :platform => "WINDOWS"
}

urlhub = "http://my-computer-ip:4444/wd/hub"
client = Selenium::WebDriver::Remote::Http::Default.new
client.timeout = 120

@webdriver = Selenium::WebDriver.for :remote, :url => urlhub, :desired_capabilities => caps, :http_client => client
@webdriver.navigate.to "https://www.google.com"
puts @webdriver.title
@webdriver.quit

Troubleshooting

If you encounter problems setting this up, please open a ticket in the issues section.

Tests

There are tests included in this project, to run them, please use mocha: mocha tests/*.js

Contributing

Fork the project, make a change, and send a pull request!

License

Licensed under the Apache License, Version 2.0

node-seleniumgrid's People

Contributors

Stargazers

Watchers

Forkers

majun8cn ronkorland yneves testpulse cyakimov zinserjan jalona sinomono karona-srun chetandg143 piyapangithub

node-seleniumgrid's Issues

Relative paths in test files are incorrect

$ mocha tests/*

module.js:340
    throw err;
          ^
Error: Cannot find module '../capabilitymatcher'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/home/shahar/ynode-seleniumgrid/tests/capabilitymatcher_test.js:2:15)

Looking at the commits history I can see that tests used to live under the lib folder but they were moved later on to the top level.

Paths should use ../lib/ instead of ../

node-seleniumgrid with tunnel to TestingBot?

Hi @testingbot,

I love how node-seleniumgrid supports connecting my own nodes to the TestingBot grid.
Now I would like to test a local site. How can I configure node-seleniumgrid to use tunnelling?

I tried first starting the node-seleniumgrid and then start the tunnel, but the tunnel .jar seems to always setup a separate grid. (which kinda makes sense)

When I try the other way around: first setting up the testing-bot tunnel, and try to connect my nodes to that, it gives me a '403 forbidden'. (which also makes sense I guess)

Any ideas how I can test local pages, on a grid with both TestingBot and local nodes connected?

Thanks!
@DV3D

Missing devDependencies

Can you please add devDependencies to package.json?
I'm trying to run the unit tests but I get:

     Uncaught TypeError: Object #<Object> has no method 'address'
      at Test.serverAddress (/home/shahar/ynode-seleniumgrid/node_modules/supertest/lib/test.js:57:18)
      at new Test (/home/shahar/ynode-seleniumgrid/node_modules/supertest/lib/test.js:38:12)
      at Object.obj.(anonymous function) [as get] (/home/shahar/ynode-seleniumgrid/node_modules/supertest/index.js:25:14)
      at /home/shahar/ynode-seleniumgrid/tests/hubstatus_test.js:11:6

I'm not sure if I'm simply using a version of supertest that's not compatible with the tests in node-seleniumgrid.

Thanks.

Is this code supported?

We are deciding on using this code in production in our internal testing infrastructure.
Do you still supporting this hub implementation: accepting PRs, fixing bugs and so on?

Ghost Driver Support

I was wondering if this Selenium Grid NodeJS implementation supports nodes running PhantomJS via GhostDriver? I did try to start one and point it to the server using

phantomjs --webdriver=<the node computer's IP>:8080 --webdriver-selenium-grid-hub=http://<server's IP>:4444

But all I end up getting is:

[ERROR - 2015-01-20T04:28:21.691Z] HUB Register - register - Problem registering with grid http://192.168.0.20:4444/: <html><head></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">OK - Welcome</pre></body></html>

Thanks in advance!