-
Notifications
You must be signed in to change notification settings - Fork 12
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
Support for x.test.x #21
Comments
This has been merged in and included in the v3.1.0 release in our Homebrew tap and on GitHub. |
Along a similar vein our in-house stlye is to have Should I open a PR to add support for |
Yeah, I was thinking about adding |
@bugeats @ashb I dug into the issues in more details. It is a side effect of the test classification regex not being correct and no fallback based on the scoring without test classification happening. So, I spun up a branch called |
From commit 771de9e
So it now returns something rather than nothing, but not even close to the right value for me - it's picked a totally different directory.
|
@ashb did you ever verify this? |
@drewdeponte Sorry, no I somehow missed the notification. Still no dice on commit 78a82b4, and the minimal repro of just those files doesn't exhibit this behaviour, so something else is about this (private, sorry can't share it) is causing the issue. Non-repro: $ mkdir -p src/lib/directives/auth/ src/lib/jwt/
$ touch {src/lib/jwt/,src/lib/directives/auth/}index{.unit.test,}.js |
Ah, add in Repro steps @drewdeponte:
Which then gives this behaviour:
|
I just released a new major release of this, v4.0.0 which should resolve these issues I believe. |
I'm surprised to see that this doesn't work:
I would expect discovery of:
... and vise-versa.
The text was updated successfully, but these errors were encountered: