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

Support automated E2E config and example scaffolding #29619

Closed
MikeMcC399 opened this issue Jun 5, 2024 · 2 comments
Closed

Support automated E2E config and example scaffolding #29619

MikeMcC399 opened this issue Jun 5, 2024 · 2 comments
Labels
type: duplicate This issue or pull request already exists

Comments

@MikeMcC399
Copy link
Contributor

What would you like?

Cypress should support an automated way of configuring and setting up E2E examples through the command line, for instance using an environment variable.

The choice of the full set of "Scaffold example specs" or the single test spec from "Create new spec" should be given.

Why is this needed?

Currently it is necessary to use cypress open, then to manually agree to the configuration, followed by selecting spec options.

This means that there is no straightforward way to automate the setup or update of a running Cypress example project. Instead, manual steps have to be described and carried out. An example of this is in the instructions factory/test-project/README.MD in the cypress-io/cypress-docker-images repo, where it is necessary to combine shell instructions with manual instructions to achieve setup:


rm -rf cypress cypress.config.js
npm install cypress@latest --no-package-lock
npx cypress open
  • Select "E2E Testing"
  • Select "Electron" browser
  • Select "Continue"
  • Select "Scaffold example specs"
  • Close all Cypress windows

Test that scaffolded specs run:

npm test

Other

No response

@jennifer-shehane
Copy link
Member

Duplicate of #619

@jennifer-shehane jennifer-shehane marked this as a duplicate of #619 Jun 5, 2024
@jennifer-shehane jennifer-shehane closed this as not planned Won't fix, can't repro, duplicate, stale Jun 5, 2024
@jennifer-shehane jennifer-shehane added the type: duplicate This issue or pull request already exists label Jun 5, 2024
@MikeMcC399
Copy link
Contributor Author

@jennifer-shehane

Sorry I missed that one in my search!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants