Dameng.Logging.TUnit
0.1.2
See the version list below for details.
dotnet add package Dameng.Logging.TUnit --version 0.1.2
NuGet\Install-Package Dameng.Logging.TUnit -Version 0.1.2
<PackageReference Include="Dameng.Logging.TUnit" Version="0.1.2" />
<PackageVersion Include="Dameng.Logging.TUnit" Version="0.1.2" />
<PackageReference Include="Dameng.Logging.TUnit" />
paket add Dameng.Logging.TUnit --version 0.1.2
#r "nuget: Dameng.Logging.TUnit, 0.1.2"
#:package Dameng.Logging.TUnit@0.1.2
#addin nuget:?package=Dameng.Logging.TUnit&version=0.1.2
#tool nuget:?package=Dameng.Logging.TUnit&version=0.1.2
Introduction
Dameng.Logging.TUnit is a NuGet package that returns an Microsoft.Extension.Logging.ILogger
that wraps around the TestContext.Current.OutputWriter
supplied by TUnit.
You can use this logger to log messages in your TUnit tests, or set to user test cases, which will be captured and displayed in the test output.
Installation
Run the following in the NuGet command line or visit the NuGet package page.
Install-Package Dameng.Logging.TUnit
Usage
You can use TestContext.Current.GetLogger()
to get an ILogger
instance that writes to the TUnit output.
using Dameng.Logging.TUnit;
using Microsoft.Extensions.Logging;
public class Tests
{
[Test]
public void Basic()
{
var logger = TestContext.Current!.GetLogger("Basic");
logger.LogCritical("This is a critical log message.");
}
}
this will output:
2025-06-29 15:20:13.198 crit: Basic [0]: This is a critical log message.
with scope:
var logger = TestContext.Current!.GetLogger(
"Scope",
includeScope: includeScope
);
using (logger.BeginScope("Scope 1"))
{
logger.LogInformation("This is scope 1 message.");
using (logger.BeginScope("Scope 2"))
{
logger.LogInformation($" This is scope 2 message");
}
logger.LogInformation("This is scope 1 message after scope 2.");
}
will output:
2025-06-29 15:26:54.394 info Scope: This is scope 1 message.
=> Scope 1
2025-06-29 15:26:54.398 info Scope: This is scope 2 message
=> Scope 1 => Scope 2
2025-06-29 15:26:54.399 info Scope: This is scope 1 message after scope 2.
=> Scope 1
with Exception:
var logger = TestContext.Current!.GetLogger(
"Exception",
includeScope: true
);
using (logger.BeginScope("Scope for exception"))
{
try
{
throw new InvalidOperationException("This is a test exception with scope.");
}
catch (Exception ex)
{
logger.LogError(ex, "An error occurred while processing the request with scope.");
}
}
will output:
2025-06-29 15:26:54.394 fail Exception: An error occurred while processing the request with scope.
=> Scope for exception
System.InvalidOperationException: This is a test exception with scope.
at Dameng.Logging.TUnit.Tests.Tests.ExceptionAndScope() in C:\Dameng.Logging.TUnit\tests\Dameng.Logging.TUnit.Tests\Tests.cs:line 68
ILogBuilder
You can also use ILogBuilder
to configure the logger with additional options.
var logger = LoggerFactory.Create(logging=>
logging.AddTUnit(TestContext.Current!)
).CreateLogger("Basic");
Configuration
Minimum Log Level
You can set the minimum log level for the logger when using TestContext.Current!.GetLogger
or ILogBuilder
.
var logger = TestContext.Current!.GetLogger("Basic",minLevel: LogLevel.Trace);
var logger = LoggerFactory.Create(logging=>
logging.AddTUnit(TestContext.Current!).SetMinimumLevel(LogLevel.Trace)
).CreateLogger("Basic");
License
This project is licensed under the MIT License. See the LICENSE file for details.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 is compatible. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- Microsoft.Extensions.Logging.Abstractions (>= 9.0.6)
- TUnit.Core (>= 0.25.21)
-
net8.0
- Microsoft.Extensions.Logging.Abstractions (>= 9.0.6)
- TUnit.Core (>= 0.25.21)
-
net9.0
- Microsoft.Extensions.Logging.Abstractions (>= 9.0.6)
- TUnit.Core (>= 0.25.21)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Initial release of Dameng.Logging.TUnit - provides ILogger integration for TUnit test framework with support for scopes, different log levels, and exception logging.