...
The path and file name of the test output. This path is relative to the workspace and the file must end in .xml (it will be appended if not). Leave blank to use the name of the first assembly. [-xml]
Assembly File Patterns
The file names or patterns to match assembly files to test.
...
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.
Include
Include Traits
Only run tests with any of the matching name/value traits. -trait
Include Methods
Only run any of the given test methods. One per line. Each method can be fully specified or use a wildcard. i.e. 'MyNamespace.MyClass.MyTestMethod' or '*.MyTestMethod'. --method
Include Classes
Only run any of the given test classes. One per line. Each class should be fully specified. i.e. 'MyNamespace.MyClass. --class
Include Namespaces
Only run any of the given test namespaces. One per line. i.e. 'MyNamespace.MySubNamespace. --namespace
Exclude
Exclude Traits
Do not run tests with any of the matching name/value traits. --notraits
...
Do not run any of the given test method. One per line. Each method can be fully specified or use a wildcard. i.e. 'MyNamespace.MyClass.MyTestMethod' or '*.MyTestMethod'. --nomethod
Exclude Classes
Do not run any of the given test classes. One per line. Each class should be fully specified i.e. 'MyNamespace.MyClass'. --noclass
Exclude Namespaces
Do not run any of the given test namespaces. One per line. 'MyNamespace.MySubNamespace'. --nonamespace
NuGet
Install XUnit To
The folder NuGet should install XUnit to.
...
The Using drop down is populated by any property collector properties whose namespace matches the pattern defined by the NuGet action. The pattern for this action is ^NuGet\..* . The default property collector searches the environment path for "NuGet.exe".
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.
...
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.
Include
Include Traits
Only run tests with any of the matching name/value traits. [-trait]
Include Methods
Only run any of the given test methods. One per line. Each method can be fully specified or use a wildcard. i.e. 'MyNamespace.MyClass.MyTestMethod' or '*.MyTestMethod'. [-method]
Include Classes
Only run any of the given test classes. One per line. Each class should be fully specified. i.e. 'MyNamespace.MyClass. [-class]
Include Namespaces
Only run any of the given test namespaces. One per line. i.e. 'MyNamespace.MySubNamespace. [-namespace]
Exclude
Exclude Traits
Do not run tests with any of the matching name/value traits. [-notraits]
Exclude Methods
Do not run any of the given test method. One per line. Each method can be fully specified or use a wildcard. i.e. 'MyNamespace.MyClass.MyTestMethod' or '*.MyTestMethod'. [-nomethod]
Exclude Classes
Do not run any of the given test classes. One per line. Each class should be fully specified i.e. 'MyNamespace.MyClass'. [-noclass]
Exclude Namespaces
Do not run any of the given test namespaces. One per line. 'MyNamespace.MySubNamespace'. [-nonamespace]
Options
Convert skipped tests into failures
If this is ticked, skipped tests are converted into failures. [-failskips]
Stop on first test failure
If this is ticked, it stops on first test failure. [-stoponfail]
Level of Parallelism
The level of parallelism. [-parallel]
Logging level
The amount of information detail to display in the build log. [–quiet | -verbose]
Enable diagnostic messages for all test assemblies.
...
Not visible if the 'Logging Level' field is set to Quiet'.
If this is ticked, it enables diagnostic messages for all test assemblies. [-diagnostics]
Fail action if any tests fail
...