Stravaig Logging Diagnostics

Diagnostics for examining logs in automated tests.

A logger for use in tests so that the messages logged can be examined in tests.

Why test logs?

This was originally developed to test that background services were emitting logs in certain scenarios. Since the logs are the one of the primary views of how a background service is working it is essentially a first class output of the service. The user interface of the service, if you prefer, where the user is the developer or support technician attempting a diagnose an issue.

It can also be useful to test that structured logs emit the correct values so that values used when querying a logging sinks (such as ElasticSearch or New Relic) are available and correct.

Other reasons to capture logs

This library also supports rendering the logs it captures, filtered in any way you see fit. This can be useful in scenarios, such as calling an ASP.NET application that will emit a deluge of logs that you are unlikely to be interested as it spins up the hosted server within the test.

Usage

This package is designed to hook into the .NET logging framework so that the logger can be easily injected into units of code, or set up in the dependency injection for larger integrated tests.