NUnit is a unit testing framework for the .NET environment. The NUnit action can be pointed to either run tests via multiple .dll files or through a .NET/NUnit project or solution.
The name that will be used to identify this action. Note that Name is auto-populated with the file names that are entered in the Files property.
Only enabled actions will run when a build is executed. If an action is disabled then it will be ignored at runtime.
This field can a contain single testable file or multiple testable files including .dll files, NUnit projects or .NET projects and solutions. All files specified are 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 absolute files such as C:\myTests and the NUnit action will point to the correct location.
This field also supports Ant Patterns to specify multiple files. For example, \Output\**tests.dll would test all .dll's that end with tests which are located in the Workspace's output folder and any of its subdirectories.
Each file/pattern must start on a new line.
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 absolute files such as C:\myTests and the NUnit action will generate the output file in the correct location.
If you've specified a Visual Studio or NUnit project then you can specify the configuration you want to test against. For example, Debug, Release, etc...
If you want to test a certain fixture, enter it here. If you leave this input empty it will test every fixture.
Select the .NET framework to run the tests under.
If any tests fail the build will be stopped and marked as failed. This option isn't applied to tests that have any errors. If a test errors then the build is stopped and marked as errored regardless of this option.
The Using drop down is populated with any property collector whose namespace matches the pattern defined by the NUnit Action. The pattern for this action is
If you create a property collector for this action, make sure you select the Path Finder PlugIn type and give it a name that will match the pattern above in blue. Example names listed here, search the table's Plugin column for "NUnit".
For more in-depth explanations on property collectors see Managing Property Collectors.
Alternatively, you can select the Custom option from the Using drop down list and specify a path in the resulting input field that will be displayed. Please read Why it's a good idea to use a property collector before using this option.