NUnit Test Logger

NUnit xml report extension for Visual Studio Test Platform.

Packages

Logger	Stable Package	Pre-release Package
NUnit

If you're looking for xunit or junit, please see https://github.com/spekt/testlogger.

Usage

NUnit logger can generate xml reports in the NUnit v3 format.

1. Add a reference to the NUnit Logger NuGet package in test project
2. Use the following command line in tests

> dotnet test --logger:nunit

3. Test results are generated in the TestResults directory relative to the test.csproj

A path for the report file can be specified as follows:

> dotnet test --logger:"nunit;LogFilePath=test-result.xml"

test-result.xml will be generated in the same directory as test.csproj.

Note: the arguments to --logger should be in quotes since ; is treated as a command delimiter in shell.

Microsoft.Testing.Platform (MTP) Support

The logger also supports Microsoft.Testing.Platform (MTP) with the following command line options:

> dotnet test -- --report-spekt-nunit --report-spekt-nunit-filename test-result.xml

The --report-spekt-nunit option can also accept configuration arguments:

> dotnet test -- --report-spekt-nunit "key1=value1;key2=value2"

Configuration

Supported configuration options include:

• LogFilePath: Sets the output file path (supports token expansion with {assembly} and {framework})

All common options to the logger is documented in the wiki. E.g. token expansion for {assembly} or {framework} in result file.

NUnit test framework settings

• If your scenario requires test case properties like Description in the xml, please enable internal properties for the nunit adapter:

dotnet test --logger:nunit -- NUnit.ShowInternalProperties=true

• NUnit test adapter also provides a mechanism to emit test result xml from the NUnit engine. You may use following commandline for the same:

dotnet test --logger:nunit -- NUnit.TestOutputXml=<foldername relative to test binary directory>

License

MIT