You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The console output can be very verbose for large repositories so I generally turn it to quiet so that Azure DevOps or GitHub Actions UI isn't flooded with thousands of lines of output. Every once in a while though, our tests encounter problems and I can see the output of stuff like long running test detection in xunit or the blame collector.
I thought it would be good to have a logger that writes all of the detailed output to a file and then if the test run fails, upload that in the hosted build environment for investigation. Here's my prototype:
This is pretty much what we do in the new testing.platform. VStest is not adding any new features, but the logger extension point is still available, so you can ship you logger in a nuget, and you don't need any new cooperation from vstest to do that. See the TrxLogger for how to implement:
The console output can be very verbose for large repositories so I generally turn it to quiet so that Azure DevOps or GitHub Actions UI isn't flooded with thousands of lines of output. Every once in a while though, our tests encounter problems and I can see the output of stuff like long running test detection in xunit or the blame collector.
I thought it would be good to have a logger that writes all of the detailed output to a file and then if the test run fails, upload that in the hosted build environment for investigation. Here's my prototype:
https://github.com/jeffkl/vstest-loggers/tree/main/src/File.TestLogger
Would this be something anyone else would want and maybe build directly into the VS test platform?
The text was updated successfully, but these errors were encountered: