Config from cypress.json is considered as cli config in the app

• Cypress Version: 1.0.3

Is this a Feature or Bug?

Bug

Current behavior:

Environment variables from cypress.json are treated as cli config, thus settings from cypress.json have higher priority than those from cypress.env.json:

domain env variable config (cypress.json.host), was provided by cypress.json not cli.

Desired behavior:

Configs from cypress.json should appear as configs from cypress.json file, not cli, so cypress.env.json config should overwrite cypress.json one.

[brian-mann]

I agree its a bit confusing - but the reason is that because there are 4 areas that can set environment variables it’s not really a direct 1:1 comparison of cypress.json. It’s more like saying - these are all the environment variables that have been set from all 4 different sources.

It’s a visual thing only so we could just update it. We’ve actually had this question / confusion at least 1 other time.

If you want submit a PR - this is just the react front end for the packages/desktop-gui. @jennifer-shehane or @chrisbreiding could also do it too.

[pawelgalazka]

Ahh… cool, ok so I do not nest in cypress.env.json now, and I changed environmentVariables key to env in cypress.json and it seems to work:

But why app interface keeps environmentVariables name ? Shouldn’t display env ? That’s a bit confusing.