This page lists the command line options for dottestcli.

Configuring the Test Configuration

-config <config_url>

This option allows you to specify the test configuration that will be used for analysis. The option must be followed by the name of a built-in, user-defined, or DTP-hosted test configuration.

Examples:

• dottestcli -config "builtin://Critical Rules"
• dottestcli -config "user://My_Config"
• dottestcli -config "dtp://New_Rules"

-listConfigs

 See Configuring Test Configurations for details.

Configuring the Input Scope

-solution <path>

This option specifies the path to the solution to be analyzed (in the .sln or .slnx format). You can use Ant-style wildcards to specify patterns.

Example:

• -solution "C:\Devel\FooSolution\FooSolution.sln"

You can use this option multiple times on the same command line  to specify multiple solutions.

-project <path>

This option specifies the path to the project to be analyzed when the solution is not provided. You can use Ant-style wildcards to specify patterns.

Example:

• -project "C:\Devel\FooSolution\FooProject.csproj"

You can use this option multiple times on the same command line  to specify multiple projects.

-website <path>

This option specifies the path to the website directory to be analyzed when the solution is not provided.

Example:

• -website "C:\Devel\MyWebsite"

You can use this option multiple times on the same command line to specify multiple resources.

-solutionConfig

This option specifies the solution configuration.

Example:

• -solutionConfig Debug

-projectConfig

This option specifies the solution configuration.

Example:

• -projectConfig Debug

-targetPlatform

This option specifies the target platform of the solution (or project) configuration.

Examples:

• -solution "C:\Devel\FooSolution\FooSolution.sln" -solutionConfig Debug -targetPlatform "Any CPU"
• -project "C:\Devel\FooSolution\FooProject.csproj" -projectConfig Debug -targetPlatform AnyCPU

-resource <path relative to the solution>

This option narrows down the primary testing scope defined with the -solution, -project, and -website options. You can specify one of the following:

• a path to a project in a solution
• a path to a directory of files in a project
• a path to a file

You can use this option multiple times on the same command line  to specify multiple resources. You can use Ant-style wildcards to specify the resource.

Examples:

• -resource "FooSolution/MyProject1"
• -resource "FooSolution/MyProject1/QuxDirectory"
• -resource "FooSolution/MyProject1/QuxDirectory/BazFile.cs"

-include <absolute path> and -exclude <absolute path>

These options narrow down the primary testing scope defined with the -solution, -project, and -website options. You can use Ant-style wildcards to specify the resource.

Example:

• -exclude "C:/Devel/FooSolution/*.Tests/**/*.*"
• -include "C:/ProductX/Solution1/src"

-reference <path>

This setting specifies the path to additional assemblies needed to resolve dependencies of the analyzed projects. Use this option if you receive an "Unable to find reference assembly" message. You can use Ant-style wildcards and relative paths to the current working directory.

Example:

• -reference C:\MySolution\ExternalAssemblies\*.dll
• -reference C:\Solution1\Assemblies2018\*.exe
• -reference C:\FooSolution\Ext\**\*.dll

-testTagFilter

This option specifies issue tracking tags that associate unit tests with development artifacts (such as bugs, tasks, feature requests, etc.) to limit the scope of test execution. If configured, dotTEST executes only tests associated with development artifacts that are provided with the -testTagFilter option. Provide the type of issue followed by one or more artifact IDs in the following format:

-testTagFilter <type>=<ID>

You can specify more than one -testTagFilter option on a command line.

Examples:

• -testTagFilter "task=123"
• -testTagFilter "task=123, 456, 789, 334"
• -testTagFilter bug="123, 667" -testTagFilter "fr=229"

See Associating Tests with Development Artifacts for details about issue tracking tags.

See Running Unit Tests for more information.

Installing Additional Components

-installAnalyzer <name;path>

 This option installs an external Roslyn analyzer that includes custom rules. You can specify one of the following:

• the name and path to the analyzer in the following format: name;path
• the path to a .lst file containing a list of analyzers, with each entry in the format: name;path

Examples:

• -installAnalyzer MyAnalyzerName;"F:\Roslyn Analyzers\MyAnalyzerName.dll"
• -installAnalyzer "F:\Roslyn Analyzers\analyzers.lst"

Example - list of analyzers:

MyAnalyzerName1;F:\Roslyn Analyzers\MyAnalyzerName1.dll

MyAnalyzerName2;F:\Roslyn Analyzers\MyAnalyzerName2.dll

MyAnalyzerName3;F:\Roslyn Analyzers\MyAnalyzerName3.dll

-uninstallAnalyzer <name>

This option uninstalls an external Roslyn analyzer. You can specify one of the following:

• the name of the analyzer
• the name and path to the analyzer in the following format: name;path
• the path to a .lst file containing a list of analyzers, with each entry in the format: name;path

See -installAnalyzer for examples.

Reporting

-report <path>

This option specifies the path to the directory where the report will be created.

-publish

This option sends the results to DTP. See Sending Results and Publishing Source Code to DTP.

Customizing Configuration

-settings <path>

This option specifies the path to a custom .properties file that includes customized settings in the following format: key=value (for example, report.format=pdf). You can use this option multiple times to specify several .properties files. Entries with the same key will be overwritten. 

Example:

• -settings Project1Config.properties

The use of a proxy is supported.

-property <key>=<value>

This option allows you to configure a single setting directly in the command line.  Use the following format: key=value.

You can use this option multiple times to configure several settings on the same command line. Earlier entries with the same key will be overwritten.

Examples:

• -property session.tag=sa_linux -property report.dtp.publish=true -property techsupport.create.on.exit=true

-showSettings

See Configuration Settings for the list of settings you can configure.

Collecting Coverage

-staticCoverage

This option specifies a path to the coverage.xml file that contains static coverage data.

-runtimeCoverage

This option specifies the path to the runtime coverage data file containing coverage collected from executed tests using the coverage agent. Alternatively, you can provide a path to a folder that contains multiple runtime coverage data files from more than one testing session.

See Application Coverage for details.

Configuring the Test Impact Analysis

-referenceReportFile

This option specifies the path to the reference report.xml file containing data from the latest run that is used as a baseline to perform Test Impact Analysis (execution of only the affected tests).

-referenceCoverageFile

This option specifies the path to the reference coverage.xml file containing data from the latest run that is used as a baseline to perform Test Impact Analysis (execution of only the affected tests).

Other Options

-machineId

This option prints your machine ID.

-language

This option specifies the UI language for a dotTEST run:

• zh-CN for Chinese
  
• ja-JP for Japanese

-encodePass <your password>

-noBuild

This option skips the building phase of a solution or project.

-out <path>

This option specifies the path to the file where the console output is saved.

-fail

This option fails the command by returning a non-zero exit code if violations or setup problems are reported (see Command Line Exit Codes for details about exit codes returned if the process fails).

-version

This option prints information about the version of the Parasoft tool you are using.

-help

This option prints the command line help.