Running tests from a specific groups
See original GitHub issue- Cypress Version: 1.0.3
Is this a Feature or Bug?
Feature
Current behavior:
There is no way to run a group of tests. We can either run tests from one file or all of them per project. The closest way to do it is to use --project
flag and define cypress.json
for each group. It feels just too much especially if we wanna to share same cypress config for couple groups.
Desired behavior:
Practical example, would be to be able to group tests into smoke tests and e2e tests and call them separately. Or sometimes just run smoke tests.
So in general being able to run group of tests, for example to run all tests from a certain subdirectory.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
TestNG Groups | How to run TestNG tests in Groups? - Tools QA
Groups in TestNG denotes the process of grouping different tests together into a straightforward group and running these tests together by ...
Read more >How to run a specific group of tests in TestNG from command ...
Groups are specified in your testNG.xml file using the <groups> tag. It can be found either under the <test> or <suite> tag. Groups...
Read more >How to group test cases in TestNG [with Examples]
You can specify your Groups using the <groups> tag in your testng.xml file, under the <test> or tag. To run a group of...
Read more >Grouping tests with Nightwatch | Developer Guide
Nightwatch makes it possible to organize your test scripts into groups and run them as needed. To group tests together just place them...
Read more >How do I have TestNG run tests in specific groups (from the ...
Is TestNG ignoring the -groups command-line argument because testng.xml says to run all the tests in the package? If so, how should I...
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 Free
Top 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
Quick workaround which we found is passing
--config integrationFolder=tests/smoke
in cli call, not sure if that’s the right way…In latest version I’ve used
"cypress:smoke:run": "export CYPRESS_integrationFolder=cypress/smoke && node_modules/.bin/cypress run",
based on @pawelgalazka comment