JUnit xml report extension for Visual Studio Test Platform.
| Logger | Stable Package | Pre-release Package |
|---|---|---|
| JUnit |  |
 |
If you're looking for Nunit, Xunit or appveyor loggers, visit following repositories:
- https://github.com/spekt/nunit.testlogger
- https://github.com/spekt/xunit.testlogger
- https://github.com/spekt/appveyor.testlogger
The JUnit Test Logger generates xml reports in the Ant Junit Format, which the JUnit 5 repository refers to as the de-facto standard. While the generated xml complies with that schema, it does not contain values in every case. For example, the logger currently does not log any properties. Please refer to a sample file to see an example. If you find that the format is missing data required by your CI/CD system, please open an issue or PR.
- Add a reference to the JUnit Logger nuget package in test project
- Use the following command line in tests
> dotnet test --test-adapter-path:. --logger:junit
- Test results are generated in the
TestResultsdirectory relative to eachtest.csprojfile.
There are several options to customize the output file name, location, and contents.
Platform Specific Recommendations:
After the logger name, command line arguments are provided as key/value pairs with the following general format. Note the quotes are required and key names are case sensitive. In case of issues, review the command line output for error messages.
> dotnet test --test-adapter-path:. --logger:"junit;key1=value1;key2=value2"
Specify the path and file relative to the .csproj file for each test project.
Note This option is not compatible with LogFileName or TestRunDirectory
- LogFilePath=artifacts\test-output.xml
- LogFilePath=artifacts\{framework}\{assembly}-test-results.xml
- LogFilePath=..\artifacts\{assembly}-test-results.xml
Specify the file name. Unless the TestRunDirectory is specified the file will be stored in the default TestResult directory, relative to the test csproj file.
- LogFileName=test-output.xml
- LogFileName={framework}-{assembly}-test-results.xml
Specify the directory, absolute or relative to the test csproj file. If the file name is not specified, it will be TestResults.xml
- TestRunDirectory=artifacts\
- TestRunDirectory=artifacts\{framework}\
This option alters the testcase name attribute. By default, this contains only the method. Class, will add the class to the name. Full, will add the assembly/namespace/class to the method. See here for an example of why this might be useful.
- MethodFormat=Default
- MethodFormat=Class
- MethodFormat=Full
When set to default, the body will contain only the exception which is captured by vstest. Verbose will prepend the body with 'Expected X, Actual Y' similar to how it is displayed in the standard test output. 'Expected X, Actual Y' are normally only contained in the failure message. Additionally, Verbose will include standard output from the test in the failure message. See here for an example of why this might be useful.
- FailureBodyFormat=Default
- FailureBodyFormat=Verbose
When set to default, file encoding will be UTF-8. Use this option if you need UTF-8 with BOM encoding.
- FileEncoding=Utf8 (This is the default, and does not need to be specified explicitly.)
- FileEncoding=Utf8Bom
By default, every test project generates an xml report with the same directory and file name. The tokens {framework} and {assembly} may be placed anywhere in the directory or file names to customize the output location. This is critical, when multiple test reports will be written to the same directory, as in the following example. Otherwise, the files would use identical names, and the second output file written would overwrite the first.
Consider following project structure:
.\Solution\MySolution.sln
|____\TestLib1\TestLib1.csproj
|____\TestLib2\TestLib2.csproj
Run Tests:
> dotnet test --test-adapter-path:. --logger:"junit;LogFilePath=..\artifacts\{assembly}-test-results.xml"
New Files:
.\Solution\
|____\artifacts
|____\TestLib1-test-results.xml
|____\TestLib2-test-results.xml
MIT