This indeed works very well:
All console output is shown in the build log.
So when you need more context on tests that succeed, you can just output them on the Console.
A practical use: testing the sending of SMS messages over HTTPS where the intermediate proxy can change and was giving different effects.
Logging the actual proxy used correlated some run-time findings. Based on that we could write better tests.
–jeroen
via: nunit – How can I view .NET trace logs in TeamCity? – Stack Overflow.
Filed under: .NET, Agile, C#, Continuous Integration, Development, MSTest, Software Development, TeamCity, Testing.NET, Unit Testing, VSTest
