TestArmada / boilerplate-nightwatch

An example magellan automated testing project with nightwatch.js tests
MIT License
51 stars 46 forks source link

Get `socket hang up` issue when i follow the same pattern here for nightwatch config #60

Closed ywangii closed 7 years ago

ywangii commented 7 years ago

This is how my sauce config looks like in nightwatch.json:

    "sauce": {
      "selenium_host": "ondemand.saucelabs.com",
      "selenium_port": 80,
      "username": "${SAUCE_USERNAME}",
      "access_key": "${SAUCE_ACCESS_KEY}",
      "use_ssl" : false,
      "silent" : true,
      "output" : true,
      "screenshots" : {
        "enabled" : false,
        "on_failure" : true,
        "path" : ""
      },
      "desiredCapabilities": {
        "browserName": "",
        "platform": "",
        "version": ""
      },
      "selenium": {
        "start_process": false
      }
    }

And when i run it through saucelab using

SAUCE_USERNAME=... SAUCE_ACCESS_KEY=... ./node_modules/.bin/magellan --env saucelabs --sauce_browser chrome_latest_Windows_10_Desktop --sauce-create-tunnels --test ...

It keeps returning me

22:09:47 Error retrieving a new session from the selenium server
22:09:47 Connection refused! Is selenium server started?
22:09:47
22:09:47 { Error: socket hang up
22:09:47     at createHangUpError (_http_client.js:254:15)
22:09:47     at Socket.socketCloseListener (_http_client.js:286:23)
22:09:47     at emitOne (events.js:101:20)
22:09:47     at Socket.emit (events.js:188:7)
22:09:47     at TCP._handle.close [as _onclose] (net.js:497:12) code: 'ECONNRESET' }

node@6.11.2 nightwatch@0.9.16

Any idea about this?