In this section:
Test configurations define how your code is analyzed and tested, including which static analysis rules are enabled, which tests to run, and other analysis parameters. dotTEST ships with built-in test configurations, but users can create and store their own test configurations in the DTP server (see the DTP documentation for details).
User-defined test configurations that are stored in DTP can be downloaded from the DTP server and stored in the <INSTALL_DIR>\configs\user directory as *.properties files.
You can specify which configuration will be run in one of the following ways:
Run dottestcli with the -config switch and specify a built-in, user-defined or DTP-hosted test configuration:
-config "builtin://Recommended Rules" -config "user://Foo Configuration" -config "dtp://Foo Team Configuration" -config "dtp://FooTeamConfig.properties" |
Alternatively, you can add the prefix of the Parasoft tool you are using to specify a DTP-hosted test configuration:
-config "dottest.dtp://Foo Team Configuration"
You can also provide a path or URL to the test configuration .properties file:
-config "C:\Devel\Configs\FooConfig.properties" -config "http://foo.bar.com/configs/FoodConfig.properties" |
For example, your command line may resemble the following:
dottestcli.exe -solution "C:\Devel\MyFooSolution\MySolution.sln" -config "builtin://Demo" -report "C:\Report" |
In the .properties file, specify the default configuration that will be run when the -config option is not used:
dottest.configuration=user://Configuration Name |
Use the -listconfigs switch to print the available test configurations.
See Built-in Test Configurations for information about available built-in test configurations.
Use RuleWizard to create custom rules. See the RuleWizard User Guide for information about RuleWizard capabilities and usage.
To use the rule, it needs to be enabled in a test configuration and the custom rule file must be located in one of the following directories: