We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm using frontend-maven-plugin to run JS tests for our project and I have the following output which is very confusing.
The logging we produce in order to trace our tests' execution is all logged as [ERROR]
ava 1.0.0-beta.6 node 10.5.0 npm 6.1.0
The text was updated successfully, but these errors were encountered:
It's to separate AVA's output from your program's output. For example with the TAP reporter we can't mix them up.
The answer might be to configure your logger to not output anything when tests are running, or to discard stderr in CI.
stderr
(I'm closing this issue for housekeeping purposes, but let's keep the conversation going.)
Sorry, something went wrong.
Can't this be managed with streams? Use one stream specifically for AVAs output and pipe it at the end to stdout or a file.
That's pretty much what we do, except that all non-AVA output is written to stderr.
I wonder if, unless --verbose is set, AVA should not print any non-AVA output. Perhaps with a message at the end that output was silenced.
--verbose
No branches or pull requests
I'm using frontend-maven-plugin to run JS tests for our project and I have the following output which is very confusing.
The logging we produce in order to trace our tests' execution is all logged as [ERROR]
ava 1.0.0-beta.6
node 10.5.0
npm 6.1.0
The text was updated successfully, but these errors were encountered: