In the past we always had often problems to manage logging mechanisms in unit tests, so I wrote ThrowAwayLogger that solves the problem.
1// field
2private ILogger _log = new ThrowAwayLogger();
3
4// call
5_log.Log(LogLevel.Information, _ex, "Test " + _message);
6}
In principle, all this can be implemented via Moq , but there are often cases where validations are not necessary and a simple mock mechanism is sufficient.
Author
BEN ABT
Ben is a Principal Software Engineer at Medialesson.de, with a strong focus on .NET and Microsoft Azure. In his professional role, he designs and builds highly scalable platforms for hybrid and cloud-based scenarios. He also advises companies and C-levels on migrating to the sovereign cloud.
He runs myCSharp.de, the largest and most active German-speaking C# community forum, actively contributes to both his own and external open-source projects, and regularly shares his knowledge through his blog, at community events, conferences, and as a writer for technical magazines.
Comments