-
Notifications
You must be signed in to change notification settings - Fork 213
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
Absolute folder path filters trigger "no test found" #1667
Comments
This seems to work fine for me on linux, can you clarify what platform you are on or provide any additional info you think might be relevant? |
It happened on Mac for me. I'm not exactly sure what else to say |
Ok, I don't have a mac to test this on, but I think @natebosch does. Although I would be very surprised if it works on linux but not mac... |
Haha, I'm not quite sure either. In any case, since this was triggered by my custom test renderer, I used a workaround and converted paths to relative ones. |
I can't reproduce this behavior. I'm on mac with the latest stable SDK ( I get the same results whether I run with no argument,
|
I am going to close this as not reproducible for now, if you can figure out a way to reproduce it we can take another look |
If that helps here's my dart version
on macos 12.2: Here's a video too: Screen.Recording.2022-02-14.at.20.28.27.mov |
We must still have some code treating |
Upgrading Dart to I created a brand new project, and for some reason with that project, absolute paths works. edit I'm too slow apparently haha |
test/pkgs/test_core/lib/src/runner/loader.dart Lines 140 to 147 in 5bbe1a8
|
Fixes #1667 The special treatment of `packages` as a directory name was from when `pub` would create a directory with that name under the package root. I think the intention was to avoid loading in tests from the packages pub downloaded. There are still cases where a directory named `packages` is created and treated specially by Dart tooling, but those use cases are limited to the web and should no longer have their `test` directories retained.
Fixes #1667 The special treatment of `packages` as a directory name was from when `pub` would create a directory with that name under the package root. I think the intention was to avoid loading in tests from the packages pub downloaded. There are still cases where a directory named `packages` is created and treated specially by Dart tooling, but those use cases are limited to the web and should no longer have their `test` directories retained.
It seems like if
dart test folderPath
is executed an absolute path instead of a relative path, thendart test
will somehow fail to execute the testsExample:
The text was updated successfully, but these errors were encountered: