You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
@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".
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:
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:
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
The text was updated successfully, but these errors were encountered: