This page lists the command line options for
Configuring the Test Configuration
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"
This option prints a list of available test configurations and can be used to obtain a valid test configuration name you can pass with the
See Configuring Test Configurations for details.
Configuring the Input Scope
This option specifies the path to the solution to be analyzed. You can use Ant-style wildcards to specify patterns. Example:
You can use this option multiple times on the same command line to specify multiple solutions.
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:
You can use this option multiple times on the same command line to specify multiple projects.
This option specifies the path to the website directory to be analyzed when the solution is not provided. Example:
You can use this option multiple times on the same command line to specify multiple resources.
This option specifies the solution configuration. Example:
This option specifies the solution configuration. Example:
This option specifies the target platform of the solution (or project) configuration. Examples:
-solutionConfig Debug -targetPlatform "Any CPU"
-projectConfig Debug -targetPlatform AnyCPU
-resource <path relative to the solution>
This option narrows down the primary testing scope defined with the
-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:
-include <absolute path> and -exclude <absolute path>
These options narrow down the primary testing scope defined with the
-website options. You can use Ant-style wildcards to specify the resource. Example:
.lstfile and pass the file with the
-excludeswitch. Each line in the file will be treated as a single entry.
This setting specifies the path to aditional 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:
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:
You can specify more than one
-testTagFilter option on a command line.
-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.See Configuring the Test Scope for details about configuring the test scope.
This option specifies the path to the directory where the report will be created.
This option sends the results to DTP. See Sending Results and Publishing Source Code to DTP.
This option specifies the path to a custom .properties file that includes customized settings in the following format:
report.format=pdf). You can use this option multiple times to specify several .properties files. Entries with the same key will be overwritten. Example:
This option allows you to configure a single setting directly in the command line. Use the following format:
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
This option prints the current settings and customizations.
See Configuration Settings for the list of settings you can configure.
This option specifies a path to the coverage.xml file that contains static coverage data.
This option specifies the path to the runtime coverage data file downloaded via CAM. 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 Web Applications for details.
Configuring the Test Impact Analysis
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).
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).
See also the known limitations of Test Impact Analysis in dotTEST.
This option prints your machine ID.
-encodepass <your password>
This option prints an encoded password that can be used in the .properties configuration file.
This option skips the building phase of a solution or project.
This option specifies the path to the file where the console output is saved.
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).
This option prints information about the version of the Parasoft tool you are using.
This option prints the command line help.