-
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
Test-like output when test file does not exist #575
Comments
This is probably due to https://github.com/novemberborn/ava/commit/9dd03d5d2b20de48e72cb59e29573dd412201b1b (see #502). There's some variance between the reporters, looks like the verbose one should render a cross. Maybe this particular exception should be treated differently in the mini reporter. Or perhaps a general case can be made when there is 1 exception and no tests where found. |
No no, this kind of top-level output from CLI should be written without reporters, as those are fatal errors. |
Not when watching though. It's legit to start a watcher even if there are no test files yet. Or to remove the only test file while the watcher is running. |
What's the status of this? A simple edit to |
If we can agree that these are not fatal errors then I think we can fix up the reporters. |
Closing because this was fixed a while back in #704. |
The output is not what it should look like (latest master):
(example.js does not exist).
First of all, notice 1 extra line at the start & end of the output. And top-level CLI errors should be displayed as:
The text was updated successfully, but these errors were encountered: