Add --config-file CLI argument

[kentcdodds]

Current behavior:

I cannot specify a configuration file path

Desired behavior:

I want to specify a configuration file path

Test code:

cypress run --config-file "/path/to/config"

Additional Info (images, stack traces, etc)

I'm building a tool for PayPal called paypal-scripts (similar to react-scripts). One of the purposes is to cover 80% of the use cases by hiding all configuration from the user of the tool so they can focus on just writing the code. If they do create a cypress.json file then we'll use that one, but for most people they should be able to just use the built-in configuration of paypal-scripts and they wont need to have and maintain a cypress.json file at all. There's honestly not a lot of configuration we'd need (mostly the baseUrl I think), but a lot of the value proposition of paypal-scripts is that people don't need to worry about configuring anything and it all just works out of the box.

I'm able to do this with eslint, babel, and many other tools, but I can't currently do it with cypress and I'd like to be able to do that if possible :) Thoughts?

[jennifer-shehane]

Would probably call the arg --configFile in keeping with the naming convention of our other file path args: https://on.cypress.io/configuration#Folders-Files

[kentcdodds]

That sounds great 👍

[brian-mann]

Yeah this has come up before in a longer thread here - #909 (comment)

I agree with the need for this. At the moment cypress is hard coded to look for the cypress.json file.

But, today -- for dynamic configuration - you could use plugins/index.js to modify all of the values before they're handed off to Cypress - https://docs.cypress.io/api/plugins/configuration-api.html

We have some examples that might satisfy your requirements today.

[kentcdodds]

The problem is that I'm trying to hide away all the configuration and if I have to tell people they have to do something fancy in plugins/index.js to make things work then that goal isn't really accomplished. So that wont work right now. I need the config to live within my package: node_modules/paypal-scripts/dist/config/cypress.json.

This isn't a huge rush for me, but I don't know that I'll be able to do any work on paypal-scripts in this regard until this has been done.

[reintroducing]

i am facing the exact same issue at SpotHero at the moment and would love to also have this option available.

[TroutZen]

Also have a use for this. I have a repo with tests for multiple services that each needs its own config file.

[brian-mann]

You can use the plugins API to programmatically alter the configuration in whatever way you want today.

You can simply have an empty cypress.json file and then merge in whatever you'd like based on whatever you'd like in whatever manner you want.

https://docs.cypress.io/api/plugins/configuration-api.html

I am confident this can handle whatever you want to throw at it.

[kentcdodds]

Probably so, but that would require that people have the plugin installed. For my use case I want people to be able to simply run: paypal-scripts e2e and it'll start things up for them without them having to have any configuration of plugins setup. The less in their filesystem the less they can mess up/have to maintain.

[vinnymac]

The docs here kind of allow for this, although I had to fix it to get it working properly in a freshly setup project on version 3.1.0.

const pathToConfigFile = path.resolve('..', 'config', `${file}.json`)

became

const pathToConfigFile = path.resolve('cypress', 'config', `${file}.json`)

It is strange to me that something like this would not be built in. It is a necessity to be able to differentiate between environments and fixtures.

[jennifer-shehane]

Also consider allowing user to pass configFile: false as part of this issue, this is a request we've seen from some users - #2711

[flotwig]

Working on this right now. Should we replace all the references to "cypress.json" in the desktop-gui with something else, to indicate that the user is using a custom config?

[Toxicable]

Would be great to see this feature in master.
It would help a lot with the Bazel intergration im working on here: bazel-contrib/rules_nodejs#607

[rodoabad]

Eagerly waiting! 👍

[SurajChande]

Eagerly waiting! 👍

Same here!

[talentlessguy]

Very much needed!

[talentlessguy]

This is cool that option is merged but it doesn't seem to be working :/

> yarn test:update
yarn run v1.17.3
$ cypress run --record --config-file update.cypress.json

  error: unknown option: --config-file

Cypress version: 3.4.1

[brian-mann]

@talentlessguy our cypress-bot comments on all closed issues indicating that they have yet to be released. This fix is slated for 3.5.0, which is why it's not in 3.4.1. Apparently the cypress-bot stopped working a couple days ago and we're fixing it.

[brian-mann]

@talentlessguy actually the cypress-bot is working, I'm not sure why it didn't comment on this issue, but here's an example of what it typically does: #4822 (comment)

[talentlessguy]

@brian-mann okay, good luck with fixing cypress-bot. I hope 3.5.0 will be released soon.

[leonfs]

Same here - this would be a great option. We tried to modify the blacklistsHosts list in the plugins file, but for some an unknown reason, the config always ended with the same blacklistsHosts that in the .json file. It must be a bug. All other properties modified by the plugin were actually showing the expected values.

[jennifer-shehane]

The code for this is done in #3246, but this has yet to be released. We'll update this issue and reference the changelog when it's released.

[cypress-bot]

Released in 3.5.0.