cypress: cypress shows error in Windows when passing args containing a url in 3.5.0

Current behavior:

After updating to Cypress 3.5.0 I’m not able to open the Cypress GUI nor to run cypress run anymore. I’m using the Vue-Plugin “cli-plugin-e2e-cypress”. I receiving the following error-message:

    Error: Command failed: C:\Users\localuser\Desktop\TEST\node_modules\cypress\bin\cypress run --config baseUrl=http://localhost:8082/
    at makeError (C:\Users\localuser\Desktop\TEST\node_modules\execa\index.js:174:9)
    at Promise.all.then.arr (C:\Users\localuser\Desktop\TEST\node_modules\execa\index.js:278:16)
    at process.internalTickCallback (internal/process/next_tick.js:77:7)
    error Command failed with exit code 1.
    info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Desired behavior:

I should be able to run my test with “cypress run” or open the GUI with “cypress open”

Steps to reproduce: (app code and test code)

upgrade from cypress 3.4.1 to 3.5.0
try “cypress run”

Versions

Cypress 3.5.0 (cli-plugin-e2e-cypress)
Windows 10
Chrome 77

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 14
Comments: 33 (9 by maintainers)

Commits related to this issue

e2e-tests: Finalize assign specs, downgrade cypress newer cypress versions do have an issue according to pass arguments to cypress via windows cmd see detailed Information: https://github.com/cypress... — committed to openkfw/TruBudget by Stezido 5 years ago

Most upvoted comments

We also have this issue. Passing any arguments (–config baseUrl=https://localhost:56949) is not possible any more. Cypress will immediately terminate.

mheiss on Oct 25, 2019

I have the same problem too on both 3.5 and 3.6 versions.

kristofferlindvall on Nov 2, 2019

Thanks for getting this fixed! Do we know approximately when this will be released?

albernhagen on Dec 6, 2019

Same here. Works on MacOS but fails on windows:

cypress open --env server=https://my.server.com

stephane-dereppe on Nov 15, 2019

Same problem here. As a workaround I could use --config-file parameter.

PetMou on Nov 5, 2019

I tested and on Linux it works. It seems that cypress.cmd is broken. On Windows cypress.cmd open without any argument works fine, as soon as a command line argument is present, it immediately exits (exit code 0).

mduft on Oct 25, 2019

Released in 3.8.0.

cypress-bot[bot] on Dec 12, 2019

Any chance this will release this week? I have some E2E test pipelines in our deploy process that I’d love to get updated waiting on this fix. If there’s anything I can do to help, I’d be happy to.

albernhagen on Dec 12, 2019

@jennifer-shehane can we please get an update as to when this will be fixed

deniseruck on Nov 21, 2019

We’re using it plain installed via npm from command line and Gradle. When passing either --config or --env or both it immediately exits (only on Windows).

mduft on Nov 5, 2019

@jennifer-shehane We are not using the cli-plugin-e2e-cypress, “just” cypress w/ webpack-preprocessor (for TypeScript support). It terminates immediately when providing the --config switch. When starting cypress w/o the config-switch it runs normally. (except the fact that base-url is not set correctly)

Example of how we are using cypress:

cypress open/run --project <subfolder> --config baseUrl=<baseUrl> --env user=<user>,password=<password>

pfoedermayr on Nov 5, 2019