...
The DotNet Test action is used to run unit tests on a .Net project using the configured test runner.
Name
A friendly name for this action (will be displayed in the actions workflow area).
Enabled
Determines if this action will be run within the relevant stage.
Project
The Path to project file or folder to test. This can be either a path to a project.json file or to a directory. If omitted, it will default to the workspace folder. Note that relative paths are rooted in the workspace folderIf a folder is specified, the folder will be searched for a file that has a file extension that ends in `proj`. Defaults to the workspace folder.
Working Folder
Optional working folder for running the executable. Defaults to the project folder.
Output Directory
The path to the folder in which to find the binaries to run the tests. Relative paths will be anchored to the workspace folder. If left empty, it will default to "/bin/[configuration]/[framework]/" for portable applications or "/bin/[configuration]/[framework]/[runtime]" for self-contained applications.
Build Base Path
Settings File
Path to file with settings to use when running tests.The path to the folder in which to place temporary outputs. Relative paths will be anchored to the workspace folder.
Using
The Using drop down is populated with any property collector whose namespace matches the pattern defined by the DotNet CLI Actions. The pattern for this action is ^DotNet.Cli.*
...
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.
Settings
Framework
Look for test binaries for a specified framework.
Configuration
The configuration to use when building the project. This defaults to "Debug" if left empty.
...
Framework
Look for test binaries for a specified runtimespecified framework.
Test Runner Arguments
Arguments to be passed to the test runner. The relevant arguments depend on the test runner specified in the project.json file.
| Info |
|---|
To display the test results in Continua CI, you need to export the test results as a file an use one of the Import Tests actions to read the results from the file. Use this field to specify the path to the results file using the relevant argument for the test runner you are using e.g. -xml for XUnit and --resultxml for NUnit. |
Options
Filter
Use to filter tests using an expression. For more information on filtering support, see VSTest TestCase filter.
Logger
The name or URL to a test results logger.
Test Adapter Path
The path to custom test adapters to use in the test run.
Test Diagnostics File
The path to test diagnostics file.
Options
No build
Tick Set this checkbox flag to skip the building phase of the project before running the teststesting process.
List tests
Set this flag to list all the tests in the project to the log.
Fail action if any tests fail
Don't tick this if you want to use a Import Unit Tests action to report on test output.
Log standard
...
output
If this is ticked, the command line output is written to the build log.
Verbose logging
Verbosity
The amount of information detail to display in the build log
...
.
Timeout (in seconds)
How long to wait for the action to finish running before timing out. Leaving this blank (or zero) will default to 86400 seconds (24 hours).
Treat failure as warning
Tick to continue build on failure marking the action with a warning status.
Ignore warnings
If this is ticked, any warnings logged will not mark the action with a warning status.
Environment
...
Multiple environment variables can be defined - one per line. These are set before the DotNet Test command line is run.
Log environment variables
If this is ticked, environment variable values are written to the build log.
Generate system environment variables
Tick this checkbox to set up a list of new environment variables prefixed with 'ContinuaCI.' for all current system expression objects and variables.
Mask sensitive variable values in system environment variables
Visible only if the 'Generate system environment variables' checkbox is ticked.
If this is ticked, the values of any variables marked as senstive sensitive will be masked with **** when setting system environment variables. Clear this to expose the values.
...