Skip to content
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

Open
brucewpaul opened this issue Feb 23, 2018 · 5 comments
Open

cypress folder being added even with custom folders set #1372

brucewpaul opened this issue Feb 23, 2018 · 5 comments
Labels
type: feature New feature that does not currently exist

Comments

@brucewpaul
Copy link

brucewpaul commented Feb 23, 2018

Current behavior:

I have the following in my cypress.json:

{
  "fileServerFolder": "./test/_integration",
  "integrationFolder": "./test/_integration/integration",
  "pluginsFile": "./test/_integration/plugins",
  "screenshotsFolder": "./test/_integration/screenshots",
  "supportFile": "./test/_integration/support",
  "videosFolder": "./test/_integration/videos",
}

but when I run cypress open, it scaffolds a cypress folder

Desired behavior:

To not scaffold a cypress if custom folders are set

How to reproduce:

run cypress open with the above conifg

  • Operating System: osx
  • Cypress Version: 2.0.3
  • Browser Version: 64
@jennifer-shehane jennifer-shehane added type: feature New feature that does not currently exist stage: proposal 💡 No work has been done of this issue labels Feb 26, 2018
@jennifer-shehane
Copy link
Member

There has definitely been internal discussion about giving more control over the scaffolding process that needs to be implemented.

@dreamyguy
Copy link

I assumed that the option (as mentioned by @brucewpaul):

  "fileServerFolder": "./test/_integration",

...which in my case is set to ./tests/e2e/cypress, would stop the scaffolding as the whole cypress thing is moved there. Did I misunderstand?

@dreamyguy
Copy link

dreamyguy commented Sep 29, 2019

I actually got Cypress to run without scaffolding with the following setup. The scripts that successfully ran are mentioned in the package.json excerpt:

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

└── tests
    ├── e2e
    │   └── cypress
    │       ├── fixtures
    │       │   └── example.json
    │       ├── integration
    │       │   └── main-heading.spec.js
    │       ├── plugins
    │       │   └── index.js
    │       └── support
    │           ├── commands.js
    │           └── index.js
    └── unit
cypress.json

@stoplion
Copy link

stoplion commented Aug 4, 2022

Is this solved?

@jennifer-shehane
Copy link
Member

I believe this should now be resolved in v10 since you can choose to not scaffold example files when calling cypress open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature New feature that does not currently exist
Projects
None yet
Development

No branches or pull requests

6 participants