-
Notifications
You must be signed in to change notification settings - Fork 212
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
dart test
failed tests could be on stderr
#2161
Comments
cc @natebosch |
I think this would also be solved by #829 I'd be nervous moving existing output from cc @jakemac53 - do you feel strongly either way about moving output to |
I do worry it would be too breaking at this time to do this in the default reporter. We could however add a new reporter which does it (could share an implementation and just configure it differently?). Or, a failure only reporter would also be fine. |
Another option could be supporting logging levels etc. |
Having reporters write to two potential outputs is also a much deeper change than a failure output reporter - would probably need to wait for #1311 |
That would pretty much be what I was looking for. |
Should I create a new issue for creating a failure-only reporter and keep this one open, or should I simply rename it to clarify? |
We can discuss the failure-only reporter, and track interest with 👍 etc, over at #829 |
I'm testing git hooks for the first time with a Dart package. My current
pre-commit
script is:If I run the tests this way, I get no output. If I remove
1>/dev/null
I get a lot of output even for completing tests.I wanted to ask if the failed tests could be on
stderr
, so I could show at least which file didn't pass the testing.The only other workarounds I could think of would be re-running all tests or running
dart test -r json
and then parsing the returned JSON somehow.dart info
The text was updated successfully, but these errors were encountered: