Skip to content
This repository has been archived by the owner on Apr 23, 2020. It is now read-only.

Unreachable Selenium server message is not always shown #113

Open
MattiSG opened this issue Mar 5, 2014 · 0 comments
Open

Unreachable Selenium server message is not always shown #113

MattiSG opened this issue Mar 5, 2014 · 0 comments

Comments

@MattiSG
Copy link
Owner

MattiSG commented Mar 5, 2014

    › src/index.js example/DuckDuckGo
    ✘   The Selenium server could not be reached
        You should start it up with a command like `java -jar selenium-server-standalone.jar`
    Get more help at <https://github.com/MattiSG/Watai/wiki/Troubleshooting>
    Error: connect ECONNREFUSED
        at errnoException (net.js:901:11)
        at Object.afterConnect [as oncomplete] (net.js:892:19)
    From previous event:
        at EventEmitter.test (/Users/mesh/Documents/Watai/src/controller/Runner.js:204:7)
        at EventEmitter.wrapper.extend.$owner (/Users/mesh/Documents/Watai/node_modules/mootools/lib/mootools-core-1.4.5-server.js:997:23)
        at /Users/mesh/Documents/Watai/src/index.js:42:18

vs

    › src/index.js test/resources/FailingSuite/
    Error: connect ECONNREFUSED
        at errnoException (net.js:901:11)
        at Object.afterConnect [as oncomplete] (net.js:892:19)
    From previous event:
        at EventEmitter.test (/Users/mesh/Documents/Watai/src/controller/Runner.js:204:7)
        at EventEmitter.wrapper.extend.$owner (/Users/mesh/Documents/Watai/node_modules/mootools/lib/mootools-core-1.4.5-server.js:997:23)
        at /Users/mesh/Documents/Watai/src/index.js:42:18
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant