Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Test Runner UI Needs Multi-Select Option #3589

Closed
SDESkowronski opened this issue Feb 26, 2019 · 2 comments
Closed

Test Runner UI Needs Multi-Select Option #3589

SDESkowronski opened this issue Feb 26, 2019 · 2 comments
Labels
type: duplicate This issue or pull request already exists

Comments

@SDESkowronski
Copy link

Current behavior:

In the test Runner UI I only find the ability to select a single test spec file to run.

Desired behavior:

I would like to be able to select multiple test specs to run.

I would also like to be able to select individual tests from a spec file to run as opposed to running the entire spec file. Yes, I know there is a .only() and .skip() function to tack onto the code, but that is not as simple a multi-select in the UI.

I actually came up with what I thought was a cool way to do this, and it works, but my manager has a tough time accepting it since it is "non-standard"...sigh.

What it would look like: Just like Windows File Explorer, double click launches whatever you have selected, single click selects, CTRL+single click adds or removes selection, shift+single click selects a range...check boxes could also be used.

Versions

Cypress v3.0.3 is what I am currently using.
Chrome v72.0.3626.109

@cypress-bot cypress-bot bot added the stage: proposal 💡 No work has been done of this issue label Feb 26, 2019
@jennifer-shehane jennifer-shehane added pkg/desktop-gui This is due to an issue in the packages/desktop-gui directory pkg/runner This is due to an issue in the packages/runner directory labels Feb 26, 2019
@royalrex
Copy link

royalrex commented Apr 1, 2019

+1
I'd love to see this feature as well.

Recently been doing a lot of API changes in our product, and then running all specs to find problem areas. After fixing issues in one test, it would be nice to rerun just that, or as @SDESkowronski proposes a way to select what it() statements to run eg. a UI for .skip() and .only()

@jennifer-shehane
Copy link
Member

There is this issue for running a subset of files: #3607

Also there is this issue for running a single test (which I think is what this issue is mostly a duplicate of) #925

Closing as duplicate.

@jennifer-shehane jennifer-shehane added type: duplicate This issue or pull request already exists and removed pkg/desktop-gui This is due to an issue in the packages/desktop-gui directory pkg/runner This is due to an issue in the packages/runner directory stage: proposal 💡 No work has been done of this issue labels Apr 1, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
type: duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants