...
When NUnit executes, the output will be stored in this file. Even when specifying multiple files to test, all of the output it put into a single file. The output file specified is relative to the agent's workspace so to reference the output directory of the workspace, you only need Output\ (not $Workspace$\Output). However you can still specify an absolute file location such as C:\myOutputFile.xml and the NUnit action will generate the output file in the correct location.
Project Configuration
The output file must end in .xml. If it does not then .xml will be appended to the end of the output file.
Run tests in separate thread
With this checked NUnit will create a separate thread for running the tests.
Project Configuration
When Project Configuration has a value it will run the NUnit tests from either If you've specified a Visual Studio or NUnit project then you can specify the configuration you want to test against. For example, rather then .dlls. This value tells NUnit which configuration should be used running the project (ie. Debug, Release, etc..). This property must be given a value when you are running NUnit against projects.
Test Fixture
If Test Fixture allows you want to specify a specific test fixture to execute. You must specify the full name of the test fixture along with the containing assembly. For example: Tests.MyTests myProject.tests.dll.
test a certain fixture, enter it here. If you leave this input empty it then NUnit will test every fixture.
.NET Framework
Select Specify which version of the .NET framework to run the tests undershould be used when running the NUnit action.
Fail action if any tests fail
If any NUnit tests fail then the build will stop and will be stopped and marked as failed. This option isn't applied to tests that have any errors. If a test errors only affects failed tests. Note that if a test is errored then the build is stopped and marked as errored, regardless of this option.
...