Cypress is not running test after launch

Current behavior

I recently installed cypress and new to this platform as well, I can see that my test runs on browser like edge, but i don’t see why it is not running in chrome.

Cypress version i have in my system Cypress package version: 8.3.1 Cypress binary version: 8.3.1 Electron version: 13.2.0 Bundled Node version: 14.16.0

Chrome version is 92.

The test running in headless and edge browser but not running in chrome.

I don’t see CY extension in the plugin area, i cleared the AppData from the documentation but still i am not able to see. Manually i added the plugin from webstore but still not working.

Below is the log after passing cmd in terminal as “npx cypress open” PS C:\LearningArea\pCypressLearning> npx cypress open Debugger attached. Debugger attached.

Debugger attached. Failed to connect to Chrome, retrying in 1 second (attempt 18/62) Failed to connect to Chrome, retrying in 1 second (attempt 19/62) Failed to connect to Chrome, retrying in 1 second (attempt 20/62) Failed to connect to Chrome, retrying in 1 second (attempt 21/62) Failed to connect to Chrome, retrying in 1 second (attempt 22/62) Failed to connect to Chrome, retrying in 1 second (attempt 23/62) Failed to connect to Chrome, retrying in 1 second (attempt 24/62) Failed to connect to Chrome, retrying in 1 second (attempt 25/62) Failed to connect to Chrome, retrying in 1 second (attempt 26/62) Failed to connect to Chrome, retrying in 1 second (attempt 27/62) Failed to connect to Chrome, retrying in 1 second (attempt 28/62) Failed to connect to Chrome, retrying in 1 second (attempt 29/62) Failed to connect to Chrome, retrying in 1 second (attempt 30/62) Failed to connect to Chrome, retrying in 1 second (attempt 31/62) Failed to connect to Chrome, retrying in 1 second (attempt 32/62) Failed to connect to Chrome, retrying in 1 second (attempt 33/62) Failed to connect to Chrome, retrying in 1 second (attempt 34/62) Failed to connect to Chrome, retrying in 1 second (attempt 35/62) Failed to connect to Chrome, retrying in 1 second (attempt 36/62) Failed to connect to Chrome, retrying in 1 second (attempt 37/62) Failed to connect to Chrome, retrying in 1 second (attempt 38/62) Failed to connect to Chrome, retrying in 1 second (attempt 39/62) Failed to connect to Chrome, retrying in 1 second (attempt 40/62) Failed to connect to Chrome, retrying in 1 second (attempt 41/62) Failed to connect to Chrome, retrying in 1 second (attempt 42/62) Failed to connect to Chrome, retrying in 1 second (attempt 43/62) Failed to connect to Chrome, retrying in 1 second (attempt 44/62) Failed to connect to Chrome, retrying in 1 second (attempt 45/62) Failed to connect to Chrome, retrying in 1 second (attempt 46/62) Failed to connect to Chrome, retrying in 1 second (attempt 47/62) Failed to connect to Chrome, retrying in 1 second (attempt 48/62) Failed to connect to Chrome, retrying in 1 second (attempt 49/62) Failed to connect to Chrome, retrying in 1 second (attempt 50/62) Failed to connect to Chrome, retrying in 1 second (attempt 51/62) Failed to connect to Chrome, retrying in 1 second (attempt 52/62) Failed to connect to Chrome, retrying in 1 second (attempt 53/62) Failed to connect to Chrome, retrying in 1 second (attempt 54/62) Failed to connect to Chrome, retrying in 1 second (attempt 55/62) Failed to connect to Chrome, retrying in 1 second (attempt 56/62) Failed to connect to Chrome, retrying in 1 second (attempt 57/62) Failed to connect to Chrome, retrying in 1 second (attempt 58/62) Failed to connect to Chrome, retrying in 1 second (attempt 59/62) Failed to connect to Chrome, retrying in 1 second (attempt 60/62) Failed to connect to Chrome, retrying in 1 second (attempt 61/62) Failed to connect to Chrome, retrying in 1 second (attempt 62/62) PS C:\LearningArea\pCypressLearning>

Cypress ui error after test failed. Title: Error launching browser

Message: Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.

This usually indicates there was a problem opening the Chrome browser.

The CDP port requested was <span class="ansi-yellow-fg">63672</span>.

Error details:

Error: connect ECONNREFUSED 127.0.0.1:63672 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)

Stack trace:

Error: Cypress failed to make a connection to the Chrome DevTools Protocol after retrying for 50 seconds.

This usually indicates there was a problem opening the Chrome browser.

The CDP port requested was 63672.

Error details:

Error: connect ECONNREFUSED 127.0.0.1:63672
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)

    at get (C:\Users\Prem.Padayachi\AppData\Local\Cypress\Cache\8.3.1\Cypress\resources\app\packages\server\lib\errors.js:1012:15)
    at Object.throwErr [as throw] (C:\Users\Prem.Padayachi\AppData\Local\Cypress\Cache\8.3.1\Cypress\resources\app\packages\server\lib\errors.js:1030:9)
    at C:\Users\Prem.Padayachi\AppData\Local\Cypress\Cache\8.3.1\Cypress\resources\app\packages\server\lib\browsers\protocol.js:113:21
    at tryCatcher (C:\Users\Prem.Padayachi\AppData\Local\Cypress\Cache\8.3.1\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\Users\Prem.Padayachi\AppData\Local\Cypress\Cache\8.3.1\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (C:\Users\Prem.Padayachi\AppData\Local\Cypress\Cache\8.3.1\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (C:\Users\Prem.Padayachi\AppData\Local\Cypress\Cache\8.3.1\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (C:\Users\Prem.Padayachi\AppData\Local\Cypress\Cache\8.3.1\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\promise.js:725:18)
    at _drainQueueStep (C:\Users\Prem.Padayachi\AppData\Local\Cypress\Cache\8.3.1\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\async.js:93:12)
    at _drainQueue (C:\Users\Prem.Padayachi\AppData\Local\Cypress\Cache\8.3.1\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\async.js:86:9)
    at Async._drainQueues (C:\Users\Prem.Padayachi\AppData\Local\Cypress\Cache\8.3.1\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\Prem.Padayachi\AppData\Local\Cypress\Cache\8.3.1\Cypress\resources\app\packages\server\node_modules\bluebird\js\release\async.js:15:14)
    at processImmediate (internal/timers.js:461:21)

Cypress UI screenshot

Chrome browser screenshot

Please help me!!

Desired behavior

I am expecting it to identify the chrome browser and start working

Test code to reproduce

/// <reference types="cypress" />

it(“Launch google”,function(){

cy.visit("https://www.google.com/")

})

it(“Searching something on google”, () =>{

cy.get('[title=Search]').type("who is prem padayachi")

cy.get('form').submit()

})

Cypress Version

8.3.1

Other

please help

[sin-to-jin]

@PrLu I’m not sure if it’s the same problem. For in my case, the cypress process that started before is still alive and does trouble, so set below script to “package.json”.

// package.json
{
  "scripts": {
    "killallcypress": "pgrep -fi cypress | xargs kill -9"
  }
}

To launch terminal, and type to “yarn run killallcypress”, so this problem is fixed in my case.

[jaisannaidu]

This was a user profile permission issue. Which I was able to resolve by installing cypress in a different folder.