This topic applies to: ✓ .NET Core 1.x SDK ✓ .NET Core 2.x SDK
dotnet test - .NET test driver used to execute unit tests.
dotnet test [<PROJECT>] [-a|--test-adapter-path] [--blame] [-c|--configuration] [--collect] [-d|--diag] [-f|--framework] [--filter] [-l|--logger] [--no-build] [--no-restore] [-o|--output] [-r|--results-directory] [-s|--settings] [-t|--list-tests] [-v|--verbosity] [-- <RunSettings arguments>] dotnet test [-h|--help]
dotnet test command is used to execute unit tests in a given project. The
dotnet test command launches the test runner console application specified for a project. The test runner executes the tests defined for a unit test framework (for example, MSTest, NUnit, or xUnit) and reports the success or failure of each test. If all tests are successful, the test runner returns 0 as an exit code; otherwise if any test fails, it returns 1. The test runner and the unit test library are packaged as NuGet packages and are restored as ordinary dependencies for the project.
Test projects specify the test runner using an ordinary
<PackageReference> element, as seen in the following sample project file:
<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>netcoreapp2.2</TargetFramework> </PropertyGroup> <ItemGroup> <PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.9.0" /> <PackageReference Include="xunit" Version="2.4.0" /> <PackageReference Include="xunit.runner.visualstudio" Version="2.4.0" /> </ItemGroup> </Project>
Path to the test project. If not specified, it defaults to current directory.
Use the custom test adapters from the specified path in the test run.
Runs the tests in blame mode. This option is helpful in isolating the problematic tests causing test host to crash. It creates an output file in the current directory as Sequence.xml that captures the order of tests execution before the crash.
Defines the build configuration. The default value is
Debug, but your project's configuration could override this default SDK setting.
Enables data collector for the test run. For more information, see Monitor and analyze test run.
Enables diagnostic mode for the test platform and write diagnostic messages to the specified file.
Looks for test binaries for a specific framework.
Filters out tests in the current project using the given expression. For more information, see the Filter option details section. For more information and examples on how to use selective unit test filtering, see Running selective unit tests.
Prints out a short help for the command.
Specifies a logger for test results.
Doesn't build the test project before running it. It also implicit sets the
Doesn't execute an implicit restore when running the command.
Directory in which to find the binaries to run.
The directory where the test results are going to be placed. If the specified directory doesn't exist, it's created.
Settings to use when running tests.
List all of the discovered tests in the current project.
Sets the verbosity level of the command. Allowed values are
Arguments passed as RunSettings configurations for the test. Arguments are specified as
[name]=[value] pairs after "-- " (note the space after --). A space is used to separate multiple
dotnet test -- MSTest.DeploymentEnabled=false MSTest.MapInconclusiveToFailed=True
For more information about RunSettings, see vstest.console.exe: Passing RunSettings args.
Run the tests in the project in the current directory:
Run the tests in the
dotnet test ~/projects/test1/test1.csproj
Run the tests in the project in the current directory and generate a test results file in the trx format:
dotnet test --logger:trx
Filter option details
<Expression> has the format
<property> is an attribute of the
Test Case. The following are the properties supported by popular unit test frameworks:
|Test Framework||Supported properties|
<operator> describes the relationship between the property and the value:
||Not exact match|
<value> is a string. All the lookups are case insensitive.
An expression without an
<operator> is automatically considered as a
FullyQualifiedName property (for example,
dotnet test --filter xyz is same as
dotnet test --filter FullyQualifiedName~xyz).
Expressions can be joined with conditional operators:
You can enclose expressions in parenthesis when using conditional operators (for example,
(Name~TestMethod1) | (Name~TestMethod2)).
For more information and examples on how to use selective unit test filtering, see Running selective unit tests.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.