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.

Sign up for GitHub

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

Jump to bottom

Cypress CLI dry run option #24230

Open
rcasperson-jc opened this issue Oct 12, 2022 · 2 comments
Open

Cypress CLI dry run option #24230

rcasperson-jc opened this issue Oct 12, 2022 · 2 comments
Labels
E2E Issue related to end-to-end testing Triaged Issue has been routed to backlog. This is not a commitment to have it prioritized by the team. type: feature New feature that does not currently exist

Comments

@rcasperson-jc
Copy link

rcasperson-jc commented Oct 12, 2022 •
edited
Loading

What would you like?

I would like to be able to see which tests Cypress will run based on tagging/spec without actually running them.

Why is this needed?

I want this because there are cases where I need different setup based on which test cases will be run. This is also especially relevant for parallelizing test runs in CI. I may need to know all of the tests that will be run, so they can be split up for parallelization.
@nagash77 nagash77 added E2E Issue related to end-to-end testing Triaged Issue has been routed to backlog. This is not a commitment to have it prioritized by the team. and removed routed-to-e2e labels Apr 19, 2023
@WellingtonBraga
Copy link

Hi, do we have any news on this one?

@wviana
Copy link

wviana commented Jul 18, 2024

Yes, I got into this because I wanted to list all tests for a a tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
E2E Issue related to end-to-end testing Triaged Issue has been routed to backlog. This is not a commitment to have it prioritized by the team. type: feature New feature that does not currently exist
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@wviana @nagash77 @WellingtonBraga @rcasperson-jc