Skip to content
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

Does --filter=SomeTest do anything when running npm run unit #3340

Closed
mpsommer opened this issue Oct 3, 2018 · 1 comment
Closed

Does --filter=SomeTest do anything when running npm run unit #3340

mpsommer opened this issue Oct 3, 2018 · 1 comment

Comments

@mpsommer
Copy link

mpsommer commented Oct 3, 2018

Steps to reproduce

Tell us about your environment:

Hello friends,

In the Writing Tests section of the CONTRIBUTING guide, there is this blurb about filtering tests:


  • To filter tests by name:
npm run unit --filter=waitFor

What is the expected result?
Not exactly sure what the expected result is. My first thought was that only tests that equal waitFor for would be run, so a subset of the 492 tests. This is not the case.

What happens instead?

What happens is that all 492 tests are run, which is the same as behavior as:

npm run unit

My question is: what does the --filter arg do when running tests? Anything? Does this belong in the documentation?

Thanks!!
P.S. I really dig Puppeteer

@aslushnikov
Copy link
Contributor

@mpsommer sorry for the confusion, that's a left-over. We removed the filtering part since we never actually used it; instead, we always "focus" tests with "fit" and "fdescribe".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants