vstest: vstest console does not show console output from a test logger for "quiet" verbosity level
Description
The test logger produces a console output vstest console does not show this output for default verbosity level (quiet)
Steps to reproduce
Install .NET Core sdk-2.1.300-rc1 or 2.1.200
Run tests from sample
Messages like ##teamcity[testStarted should be in the stdOut
Expected behavior
Test Logger console output should be visible for any verbosity level
Actual behavior
Test Logger console output is not visible for quiet verbosity level
Diagnostic logs
Environment
Windows 10 dotnet --version 2.1.300-rc1-008673 2.1.200
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 24 (14 by maintainers)
@mayankbansal018 vstest shows stdOut from loggers in all modes (including
quiet) for SDK 2.1.104 and for previous versions. I’ve attached the sample for 2.1.104 Users often want to minimize output but they want have CI integration Also it will be great to have the same behaviour fordotnet test,dotnet msbuild /t:vstest,dotnet vstestThat wasn’t required for 2.1.1xx and earlier versions, and also that would increase the MSBuild verbosity, which I don’t want to do. As mentioned above, this is a breaking change for CI integrations that parse the output, like TeamCity.
I think it is a breaking change. Some CI are using stdOut for integration and obviously the integration will be broken in the quiet mode. Moreover there are no way to notify about it from the logger side. Is the any way to show messages in the stdOut from loggers?