Support for --spec with "cypress open"
See original GitHub issueCurrent behavior:
--spec
flag only seems to work with the cypress run
command.
Desired behavior:
Would be nice to also have this in cypress open
command. In case we have several subfolders under integrations
folder to distinguish types of tests, and we want to work only on one specific suite. At the moment we can’t use the “Run all tests” since it will run everything.
Versions
Cypress 3.0.1
Issue Analytics
- State:
- Created 5 years ago
- Reactions:40
- Comments:17 (12 by maintainers)
Top Results From Across the Web
Command Line - Cypress Documentation
--no-exit, Keep Cypress open after tests in a spec file run. --parallel, Run recorded specs ... This can help distinguish groups of specs...
Read more >Run All Specs in Cypress v10 - Gleb Bahmutov
Click on the "all.cy.js" spec in Cypress and voilà - you got all your specs running together, just like the good old days....
Read more >Cypress- Test Runner - Tools QA
After you open the Cypress, the Test Runner window will open, which will show the test case “cypressTest1.js”, as shown below. Since in...
Read more >Cypress 10 - How to run all tests in one go? - Stack Overflow
During cypress open, the ability to "Run all specs" and "Run filtered specs" has been removed. Please leave feedback around the removal of ......
Read more >Cypress.io - Open Source Cross-Platform End-to-End Test ...
Developers seem to love writing Cypress tests and watching them run. This is mainly because the test runner watched the spec files and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m currently utilizing a separate config file and ignoreTestFiles to implement this. Same can be done with a config parameter though.
NPM scripts
I use a separate config file because I want to separate the env vars too. same thing, but move ignoreTestFiles to your config file and use
-c config.e2e.json
and-c config.unit.json
to override the default config.json optionWe are in the same need for this option. Would be a great addition to have.