-
Notifications
You must be signed in to change notification settings - Fork 20
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
Files with no included tests are still processed #256
Comments
@jrnail23 I have the same issue so I tried to take a look at this and see how it can be optimized. As isThe implementation based on the typescript preprocessor relies on loading the file via imports. It needs to, in order to parse the tags from each test and confirm if that test needs to be run or not. In the current implementation all of the invoked files will have to be parsed by (at least) the typescript preprocessor. AlternativeI think it would be necessary to run a command that parses all the files and outputs a configuration file listing key/value pairs for tag/files. With that configuration file generated we could hypothetically inject ourselves into Cypress file exclusion policies (maybe). |
Apparently @cypress/grep has this implemented already. |
oh, this looks great, thanks @mihai-stancu! |
Definitely cypress-tags should implemented what is on grep, is there any |
I wanted to surface @bquercia's comment in Issue #35, since it's in a closed issue (and thus easily overlooked):
I just experienced this myself upon my first use of
cypress-tags
, and yes, the processing of files containing no included tests is pretty time consuming, particularly when you've got lots of them. It would be great to somehow exclude them entirely, perhaps via pre-processing?The text was updated successfully, but these errors were encountered: