In this section:
configuration.dir.builtin
This setting specifies the path to the directory that contains built-in test configurations.
Acceptable Values
| [path] | The path to the folder where the built-in test configurations are stored. |
|---|
Example Usage
configuration.dir.builtin=C:\\parasoft\\dottest\\configs\\builtin
configuration.dir.user
This setting specifies the path to the directory that contains user-defined test configurations.
Acceptable Values
| [path] | The path to the folder where user-defined test configurations are stored. |
|---|
Example Usage
configuration.dir.user=C:\\parasoft\\dottest\\configs\\user
dottest.configuration
This setting allows you to specify the test configuration that will be used for analysis if the -config option is not specified (see Configuring Test Configurations for details).
Acceptable Values
| [configuration name] | The name of a built-in, user-defined or DTP-hosted test configuration. |
|---|
Example Usage
The following configuration will run the analysis with the Recommended Rules configuration when the -config option is not specified:
dottest.configuration=builtin://Recommended Rules
dottest.rulewizard.enforceold.msil
This setting allows you to specify which infrastructure will be used during analysis to execute the MSIL RuleWizard rules.
Acceptable Values
| true | Legacy infrastructure will be used (not supporting .NET projects) |
|---|---|
| false | Default. Roslyn engine will be used (supporting .NET projects) |
Example Usage
dottest.rulewizard.enforceold.msil=false
Related
rule.dir.user
This setting specifies the location of user-defined coding standard rules and rule mapping files.
Acceptable Values
| [path] | The path to the directory that contains custom rules and rule mapping files. |
|---|
Example Usage
rule.dir.user=C:\\parasoft\\my_rulemap
Related
rules.mappings
This setting allows you to specify which rule mapping is applied to your test configurations.
Acceptable Values
| default | Default. Local and DTP test configurations are customized with corresponding rule mapping (stored locally or on DTP, respectively). |
|---|---|
| all | Ensures backward compatibility for versions earlier than 10.4. Any configured rule mapping (local or DTP-shared) is applied to both local and DTP configurations. |
Example Usage
The following configuration will merge rule mapping information specified locally and on DTP:
rules.mappings=all
