barbados-clemens
commented
2 years ago do you have a cypress.json in the root of your workspace? if so can you delete it/rename it?
Closed SuneRadich closed 2 years ago
barbados-clemens
commented
2 years ago do you have a cypress.json in the root of your workspace? if so can you delete it/rename it?
SuneRadich
commented
2 years ago Yes I did. If I remove that file, my e2e tests run again. Can I convert the global json file to a cypress.config.ts file, and expect the config options to be picked up by all my libraries?
barbados-clemens
commented
2 years ago I'm unsure, as that's not a setup I'm familar with. you can try to see if it auto-matically works. if not I'd recommend just importing that file and spreading it into your config. i.e.
// root level cypress.config.ts
export default defineConfig({
// your default options you want to apply for everything
})// in your project level cypress.config.ts
import workspacePreset from '../../cypress.config'
export default defineConfig({
...workspacePreset
// rest of the config that's there today.
})more context on what's happening is ts-node is resolving your cypress.json instead of the cypress node_module.
you can verify this via using the ts-node REPL (or at least in my testing) and typing require('cypress') which will return the json, but if you type it again it'll return the actual cypress node_module.
SuneRadich
commented
2 years ago I would hate to manually have to add my global settings, more specifically configuration for test-reporting for our CI setup. If its a manual task, then I have to do it for all our many libs and apps - but then also to all newly created libs.
I thought having a root-level cypress.json was the way to handle global settings?
barbados-clemens
commented
2 years ago I'm not familiar with what is the 'correct' way to have global settings for cypress, as it was only recently I realize the root cypress.json file would "auto-magically" get included in all projects.
I would personally do what I described above as it's explicit in what is/isn't included in a given config so it's understood what influences the given cypress configuration.
did you try having a root cypress.config.ts to see if it's also magically included?
I can also look into adding this as apart of the migration to convert the root config and add to every project since that would mimic the same behavior as v9 (assuming the root cypress.config.ts isn't included)
I'd also look at providing a better error when cypress runs into this error of not being able to find defineConfig and a root cypress.json is found.
SuneRadich
commented
2 years ago I'll make a test to see if a global file still works as previous, I'll let you know how it goes.
barbados-clemens
commented
2 years ago Talked with the cypress folks about the best way to share a root level config across projects,
we are both in agreement that creating a root cypress config file (i.e. cypress.shared-config.ts) and then importing and spreading that in your project local config would be the way to go.
another option is to use the .env file at the root to inject CYPRESS_ env vars that override the config, though this is less explicit and could run into some confusion trying to debug how a value is set across your projects. I'd go for the explicit way.
SuneRadich
commented
2 years ago I will find a way to manage any global config I might need. For now we live without it.
github-actions[bot]
commented
1 year ago This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
Current Behavior
I have just migrated our nx repo to the latest nx, and in turn also Angular 14. Everything seems to be running as expected. I then proceeded to run the migration to update the Cypress setup to v.10.
The generator runs without any errors, but trying to run an e2e test afterwards results in an error.
Steps I have tried without success:
Deleting package-lock.json, and rerunning
npm installRunningnpm dedupePinning cypress version 10.2.0 in package.jsonExpected Behavior
After having run the generator to migrate the cypress setup to 10, I expect an existing e2e setup to run.
Steps to Reproduce
Make sure you have an nx 14.5.4 setup Run the
nx g @nrwl/cypress:migrate-to-cypress-10as described on https://nx.dev/cypress/v10-migration-guide Run an existing e2e projectnx e2e PROJECT-NAME-e2e. I can see from the log, that it correctly starts up a Storybook, but it fails when running cypress.Failure Logs
I see the following error stack trace:
Environment
Dependencies in package.json