-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
@cypress/grep grepFilteredSpecs flag doesn't pre-filter specs #28455
Comments
I'm experiencing this same behavior. Node: 18.18.2
The console output shows the following which is indicating that it's properly registering the plug-in:
|
Did anyone find solution or any workaround for this? |
We are having the same issue. In our pipeline the tests will be filtered on runtime, so all spec files are run, even though only a few tests need to run. Output in pipeline will only show It seems the config set as I have tried checking debug logs and this confirms my suspicion that it is ignored. When adding the filter config to my run command instead of to my config file and run the tests with Cypress open it will work, but if I run headless it will be ignored |
We are facing the same issue as well. A lot time time is wasted during execution because of this issue. Any workarounds found yet ? |
For me it worked again after moving the grep env options from the common config to the environment specific config, See #26642 |
Current behavior
Cypress will queue and individually skip all specs at runtime, which wastes a significant amount of time.
Desired behavior
Passing
grepFilterSpecs=true
to Cypress should pre-filter specs, meaning that they aren't queued up when callingcypress run
.Test code to reproduce
I went ahead and make a fork of cypress-realworld-app for an immediately reproducible example: https://github.com/MatthewClark2/cypress-realworld-app. It includes
@cypress/grep
as well and tags two describe blocks with thesmoke
tag.Executing cypress with
yarn run cypress:run --env grepTags=smoke
will find all 21 specs included in the sample project and execute them.Cypress Version
13.5.1
Node version
20.10.0
Operating System
Fedora 38 Workstation Edition
Debug Logs
No response
Other
No response
The text was updated successfully, but these errors were encountered: