Tests from example_spec.js don't run in Chrome after newly installed cypress

• Operating System: macOS Sierra 10.12.6
• Cypress Version: 0.20.1
• Browser Version: Chrome 61.0.3163.91

Is this a Feature or Bug?

Bug

Current behavior:

Clicking example_spec.js opens up chrome browser but no tests appear. Theres also a console.warn stating “WebSocket connection to ‘ws://localhost:8080/__socket.io/?EIO=3&transport=websocket’ failed: WebSocket is closed before the connection is established.”

Desired behavior:

I’d expect the tests that are included in the example_spec.js would run in browser. instead, nothing appears in the browser

How to reproduce:

• Fresh install of cypress via npm i -D cypress.
• run node_modules/.bin/cypress open from command line
• click example_spec.js in integration tests list
• notice that chrome opens, however nothing ever shows up, tests aren’t run

[2fat2kidnap]

So I had the same issue: launching a Cypress test would open both the Chrome and Electron browser, but nothing would happen, their pages would remain blank. In the Chrome console, I would see that the Websocket connection could not connect, as the WebSocket would close before the connection would be established.

Turns out that the problem was that for some reason, obscure to me, and almost certainly completely unrelated to Cypress, my hosts file on macOS got removed. That meant that the routing of localhost -> 127.0.0.1 got nuked, and Cypress relies on this mapping. It launches the browser with the assumption that it will find the test runner at localhost, which should be at 127.0.0.1 of course, in most cases anyways.

In short, if you’re seeing this, maybe check your hosts file just in case?

[mcMickJuice]

This was an issue with my hosts file. I had 127.0.0.1 mapped to a url that mapped to docker but not to localhost. After adding localhost to map to ip4, everything worked!