Closed mklinke closed 1 year ago
Hi @mklinke , thanks for opening this issue and the detailed explanation! I have confirmed your issue is indeed a bug introduced during our transition to the new cypress.config.js
config format for version 10.0.0. This seems related to #22245 and #22430 , but also identifies that we are improperly labeling the source of config overrides that are applied (baseUrl marked as from 'config' even though the value comes from CLI, fixturesFolder marked as from CLI but value is from config).
This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.
This issue has been closed due to inactivity.
Current behavior
It's not possible to override fixturesFolder via the CLI if it's configured in
cypress.config.js
. If you remove the property from the file, however, the value from the CLI is picked up.Desired behavior
The value passed in from the CLI should always override the values in the config file, just like for the other properties, e.g.
baseUrl
where this is working as expected.Test code to reproduce
Create a new project by opening Cypress in an empty folder and initiating E2E testing to generate the default files:
Change the
cypress.config.js
to have this content (only added fixturesFolder):Try to override fixturesFolder via CLI:
The CLI override is ignored and the value is still as configured in
cypress.config.js
. Please note that the Cypress UI still recognizes that the value should be overridden by marking it as red, but the value is still the one configured incypress.config.js
, ie.src/fixtures
instead ofsome/other/folder
.Cypress Version
10.6.0
Node version
v16.15.1
Operating System
Linux 5.10.102.1-microsoft-standard-WSL2 #1 SMP Wed Mar 2 00:30:59 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Debug Logs
Other
No response