-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
testMatch should find tests in .folders #3006
Conversation
Seems like this fails on travis, you might need to sort something there. |
Codecov Report
@@ Coverage Diff @@
## master #3006 +/- ##
=======================================
Coverage 67.86% 67.86%
=======================================
Files 147 147
Lines 5349 5349
=======================================
Hits 3630 3630
Misses 1719 1719
Continue to review full report at Codecov.
|
Thanks! Would you mind auditing the other places we use micromatch in to make sure we cover everything? |
Sure thing
…On Mon, Feb 27, 2017, 02:16 Christoph Pojer ***@***.***> wrote:
Thanks! Would you mind auditing the other places we use micromatch in to
make sure we cover everything?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3006 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAEEtGL-6mGR31rnCE7wEvBx30mcVdqOks5rgjIDgaJpZM4MMWTk>
.
|
* testMatch should find tests in .folders * dont depend on order of paths in tests
* testMatch should find tests in .folders * dont depend on order of paths in tests
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
When a test is inside a folder that's name starts with
.
, they are ignored bytestMatch
but are correctly found bytestRegex
. It's even more obscure if the entire project is checked out below a dot-folder, in which case all tests are ignored bytestMatch
which is now the default way of finding tests.Test plan
yarn test