-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Provide feedback in reporter when files are launched, but contain no matching tests #2246
Comments
|
I'm running into this too. Now I'm restructuring my tests directories so that I can skip end2end tests and only run (specific) unit tests with a different ava command. It's a bit weird for a user that I'm matching 1 test (which I do a lot, because tests break) and it still starts up all the unused test files and all their expensive initialization. |
@novemberborn maybe this a bad idea and certainly not very elegant, but if |
No, because we allow test titles to be generated. There would be users who'd only encounter false negatives (i.e. test files aren't selected).
|
Both due to the age of this issue, and the state of our reporters, I've decided to roll this into #2501. |
Description
When using
--match
ava seems to spend a lot of time on files that aren't going to be run.Running with and without yarn takes the same length, I've verified this by using
time
.The passing test shows in the console within a second or so of the tests starting. It then spends the next 30s doing "nothing". If I hit CTRL + C before it finishes it shows
x test files were skipped.
.Possibly related? #1288
SIGINT
Debug logs
The text was updated successfully, but these errors were encountered: