ERR_CONNECTION_CLOSED (-100) loading 'https://app/__/#/tests/integration/home.test.js'

Current behavior:

Cypress seems to be trying to read the test files from entirely the wrong place (the HTTPS version of the CYPRESS_BASE_URL environment variable and the tests/ directory), when I run it in a docker-compose network. As the app I’m testing doesn’t serve those files, this fails.

When I run the E2E tests normally, they pass: https://circleci.com/gh/textbook/starter-kit/443

However, when I run them in a network using docker-compose, they crash https://circleci.com/gh/textbook/starter-kit/437

The error message is:

ERR_CONNECTION_CLOSED (-100) loading 'https://app/__/#/tests/integration/home.test.js'

which suggests that Cypress is looking for the test files at the CYPRESS_BASE_URL and in the wrong directory; in that project (https://github.com/textbook/starter-kit) my integrationFolder is /e2e/integration.

It also mentions Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank" as Cypress starts - I don’t know if this is related, but it doesn’t happen in the success case.

Desired behavior:

I would like the Docker version to behave normally; I use this setup to regression test my code against multiple versions of Node.

Steps to reproduce: (app code and test code)

Test example repo: https://github.com/textbook/cypress-test-tiny/tree/recreate-base-url-issue

If you run Cypress in the container network (npm run cypress:docker), it fails with an error similar to the above complaint (and again looks in /tests, not /cypress):

ERR_CONNECTION_CLOSED (-100) loading 'https://app/__/#/tests/integration/spec.js'

If you start the app (npm start) and then run Cypress with a base URL (CYPRESS_BASE_URL=http://localhost:3000 npm run cypress:run), it seems fine, suggesting that it’s not just the setting of the URL that’s the problem.

Versions

Cypress: 3.5.0 (I noticed this because it started failing when Dependabot PRd the upgrade: textbook/starter-kit#24) OS: macOS 10.14.6 locally, also fails on CircleCI remotely

This happens with both cypress/included:3.5.0 and cypress/included:3.3.1; my first assumption was the problem was in trying to run Cypress 3.5 in the older image, but upgrading didn’t help.

[6a616e]

Wow, I had the exact same problem. This really needs to be fixed or at least a warning should be displayed. I have wasted quite some time before finding this. Thanks for sharing @Hulkmaster

[Hulkmaster]

after some testing i found out that it had been broken here cypress/included:3.8.1 -> cypress/included:3.8.2