We will illustrate the practical usage of the FakeLogger nuget library and demonstrate how to use FakeLogger to test logging code

Codemaze's platform is  dedicated to providing insights and resources for developers, focusing on web development, software architecture, and DevOps practices. Through articles, tutorials, and case studies, Codemaze offers insights into building scalable and maintainable software solutions. Developers can learn about frontend frameworks, backend technologies, and deployment strategies to improve their coding skills and advance their careers.

Code Maze

This post emphasizes the importance of integrating logging into unit tests in .NET applications. It explains the use of FakeLogger to test logging code, providing a comparison with the classical approach using Mock.Verify. The post includes sample code for both methodologies, highlights the properties and setup of FakeLogger, and gives examples of how FakeLogger simplifies the task of validating log messages for different scenarios.

How to Use FakeLogger to Test Logging Code in .NET

I understand the idea but is it a good practice to test logging ?
Usually a log error comes with an error so we need to test the error itself not the log

Logging is not Always and only for errors.
Logging is useful for tracking useful information about your system operations. Logging useful information like how long operations take, the frequency operations get called, how long your system is running and correlating activity between systems. Are all useful examples of how logging can be used besides just logging errors.
Capturing information like that can be useful to help developers make meaningful improvements and optimisations to code over time.
Testing that your logging is actually working and that the messages are correct, is important.