-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cypress folder being added even with custom folders set #1372
Comments
There has definitely been internal discussion about giving more control over the scaffolding process that needs to be implemented.
|
I assumed that the option (as mentioned by @brucewpaul):
...which in my case is set to |
I actually got Cypress to run without scaffolding with the following setup. The scripts that successfully ran are mentioned in the cypress.json (at project's root){
"fileServerFolder": "tests/e2e/cypress",
"fixturesFolder": "tests/e2e/cypress/fixtures",
"integrationFolder": "tests/e2e/cypress/integration",
"pluginsFile": "tests/e2e/cypress/plugins/index.js",
"screenshotsFolder": "tests/e2e/cypress/screenshots",
"supportFile": "tests/e2e/cypress/support/index.js",
"videosFolder": "tests/e2e/cypress/videos"
} package.json "devDependencies": {
"cypress": "^3.4.1"
},
"scripts": {
"test:e2e:open": "cypress open --config fileServerFolder=tests/e2e/cypress",
"test:e2e:run": "cypress run --config fileServerFolder=tests/e2e/cypress"
} File structure
|
Is this solved? |
I believe this should now be resolved in v10 since you can choose to not scaffold example files when calling |
Current behavior:
I have the following in my cypress.json:
but when I run
cypress open
, it scaffolds a cypress folderDesired behavior:
To not scaffold a cypress if custom folders are set
How to reproduce:
run
cypress open
with the above conifgThe text was updated successfully, but these errors were encountered: