Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chrome browser testing doesn't run and reports "ERROR: Error: socket hang up" #23

Open
ericclack opened this issue Nov 14, 2016 · 9 comments

Comments

@ericclack
Copy link

Hi,
I'm trying to run through the Getting Started guide here:
http://dalekjs.com/pages/getStarted.html

I'm running on Mac 10.11.6 with recent npm, node, etc.

Here's what I'm trying with errors report following command...

$ npm run browsertest

> node-react-proto@0.0.3 browsertest /Users/eric/Code/JavaScript/node-react-proto
> dalek browsertest/test-homepage.js -b chrome

Running tests
Running Browser: Google Chrome
>> ERROR: Error: socket hang up
>> ERROR: Error: socket hang up

Here's my test case...

module.exports = {
    'Test homepage': function (test) {
        test
            .open('http://www.google.com/')
            .assert.title().to.contain('Prototype')
            .done();
    }
};

The browser does pop up, but with 'data:,' in the URL bar and no pages loaded.

Let me know if you need any additional info.

@truedat101
Copy link

@davicitoafc did you find a solution to this problem? It all used to work, about a year ago, and when we tested recently on a new system, it was not working w/ Chrome. Did you try with a diff browser?

@itsMattShull
Copy link

I'm having this problem as well. Just started today.

@itsMattShull
Copy link

firefox doesn't work and chrome:canary doesn't work.

@bpeacock
Copy link

bpeacock commented Feb 8, 2017

Same problem here, it worked several months ago when I first wrote the tests but now I get a socket error.

@beechit
Copy link

beechit commented Feb 20, 2017

same problem here on a fresh install.

@jamesespie
Copy link

I had this issue. A manual update of chromedriver, rather than the version npm installed, seemed to get around / fix.
(download from google - https://sites.google.com/a/chromium.org/chromedriver/downloads)

@bpeacock
Copy link

For reference, this file is located under node_modules/dalek-browser-chrome/lib/bin/chromedriver

@lkkushan101
Copy link

Hi Guys,
I had the same issue. But managed to copy the latest chrome driver to node_modules/dalek-browser-chrome/lib/bin/chromedriver. Worked perfectly.

@truedat101
Copy link

We switched to nightwatchjs. Works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants