-
Notifications
You must be signed in to change notification settings - Fork 322
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
dotnet-test prints error stacktrace outside context #285
Comments
Triage: combine the Failed text and error message into stderr. |
(some more thoughts as I read more about this) As per posix standard, stderr should be used for writing diagnostic/error messages. IMHO test failures don't fall into diagnostic category, they are part of the core functionality that runner provides (to run and report test results). It is expected some tests will pass, some will fail. Secondly, putting failed tests on stdout allows other tools to process it from a pipe. However, an adapter could fail to discover tests because it couldn't load an assembly; or testhost may not start. This is unexpected and should go into error. Similarly if the test assembly doesn't exist, message should be written into error stream. E.g. here's how
|
Description
dotnet test
should print the stack trace for a failed test along with the Failed test. Currently it is printed after all the test results show up. This may confuse user.Steps to reproduce
dotnet test
Expected behavior
Actual behavior
Environment
vstest repo at 9da5eb8
The text was updated successfully, but these errors were encountered: