In this section:

console.verbosity.level

This setting determines the amount of detail output to the console during analysis. 

Acceptable Values

lowErrors and basic information about the current steps and status (done, failed, up-to-date) are shown.
normalDefault. Shows the same information as the low setting, but also includes command lines executed and issues reported during test and analysis.
highShows the same information as normal, but also includes warnings.

Example Usage

The following configuration outputs the most detail about the execution:

console.verbosity.level=high

dottest.build.nobuild

This setting disables/ enables build of the tested solution or projects. If enabled, the building phase is skipped during analysis. 

Acceptable Values

trueThe building phase will be skipped during analysis.
falseDefault. The tested solution or project will be built.

Example Usage

The following configuration disables building of the project/solution:

dottest.build.nobuild=true

dottest.build.builder_id

This setting specifies which builder will be used to build solutions and projects before they are analyzed by dotTEST.

Acceptable Values

dotnetSolutions and projects will be built with .NET Core SDK or .NET SDK.
msbuild

Solutions and projects will be built with MSBuild.

visualstudio

Solutions and projects will be built with Visual Studio.

Example Usage

The following configuration specifies that MSBuild will be used to build solutions and projects before the analysis.

dottest.build.builder_id=msbuild

Related

dottest.build.dotnet_path

This setting specifies the path to the .NET Core SDK executable.

Acceptable Values

[path]

The path to the dotnet.exe on your system.

Example Usage

dottest.build.dotnet_path=C\:\\dotnet\\dotnet.exe

dottest.build.solution_config

This setting specifies the solution configuration.

Acceptable Values

[solution configuration]

The name of the solution configuration.

Example Usage

The following configuration specifies that the solution configuration is "Release":

dottest.build.solution_config=Release

dottest.package.restore_timeout

This setting specifies the timeout value for restoring packages before the building phase.

Acceptable Values

[time in seconds]The timeout for restoring packages. The default value is 360.

Related

dottest.fail.setup.problems

This setting enables or disables returning the 0x40 exit code, which indicates that setup problems were reported when the process failed.

Acceptable Values

trueThe process will exit with 0x40 if setup problems are reported.
falseDefault. The process will never exit with the 0x40.

Related

file.encoding.mode

This setting specifies how file encoding is determined.

Acceptable Values

defaultEnables use of system properties.
autoEnables automatic detection of encoding for the Far-East languages specified with the file.encoding.lang property.
userEnables use of specified encoding by the file.encoding.name property.

Example Usage

The following configuration enables file encoding based on the system settings:

file.encoding.mode=default

file.encoding.lang

This setting allows you to specify the language that will be automatically detected for file encoding. It requires the file.encoding.mode property to be set to auto.

Acceptable Values

1Japanese
2Chinese
3Simplified Chinese
4Traditional Chinese
5Korean

Example Usage

The following configuration enables Japanese encoding:

file.encoding.mode=auto
file.encoding.lang=1

file.encoding.name

This setting allows you to configure file encoding other than specified in the system settings. It requires the file.encoding.mode property to be set to user.

Acceptable Values

[encoding name]

The name of the encoding, for example ASCII-US, UTF-8, UTF-16, UTF-16LE, UTF-16BE.

Example Usage

The following configuration enables encoding in UTF-16.

file.encoding.mode=user
file.encoding.name=UTF-16

local.storage.dir

This setting specifies where analysis-related data should be stored (temporary data, data caches etc.)

Acceptable Values

[path]The path to the folder where the data will be saved.

Example Usage

The following configuration stores the data in the temp folder:

local.storage.dir=C:\\parasoft\\temp

parallel.mode

This determines which parallel processing mode is used. You may want to configure this setting to optimize testing and analysis execution according to your build schedule in CI environments.

Acceptable Values

disabledOnly one of the available CPUs
autoDefault. Allows the tool to control parallel processing settings.
manualAllows you to manually configure parallel processing settings to suit your specific needs.

Example Usage

The following configuration disables parallel processing.

parallel.mode=disabled

Related

parallel.no_memory_limit

This setting enables/disables additional limits on the memory consumed by parallel processing.

Acceptable Values

trueThere will be no additional limits on the memory consumed by parallel processing.
falseDefault. Memory consumption associated with parallel processing will be limited.

Example Usage

The following configuration allows for unlimited memory consumption by parallel processes (within system limits).

parallel.no_memory_limit=true

Related

parallel.free_memory_limit

This setting specifies the amount of memory that should be kept free in low memory conditions to ensure that free memory is available for other processes.

Acceptable Values

[percentage]

The percentage of the total memory available for the application. The default is 25.

Example Usage

The following configuration ensures that 30% of the total memory of the application will be available for other processes.

parallel.free_memory_limit=30

parallel.max_threads

This setting specifies the maximum number of parallel threads that can be executed simultaneously. The actual number of parallel threads is determined by the number of CPUs, available memory, and license settings.

Acceptable Values

[number]

The maximum number of simultaneously executed parallel threads. The default value is equal to the number of CPUs.

Example Usage

The following configuration allows you to simultaneously execute two parallel threads:

parallel.max_threads=2


parasoft.user

This setting specifies a custom user name that will be associated with Parasoft artifacts, such as findings and data sent to DTP.

Acceptable Values

[name]A custom user name.

Example Usage

The following configuration overrides the local user name configured in your system with a custom name "T12":

parasoft.user=T12

settings.validation

This setting enables/disables settings validation.

Acceptable Values

trueDetault. Errors in the settings format will be reported.
falseErrors in the settings format will not be reported.

Example Usage

The following configuration disables reporting errors in the settings format:

settings.validation=false

settings.rules.file.dottest

This setting specifies the path to a file that contains additional rules for settings validation. The file should follow the .properties format and list the settings with their valid values (see Example Usage for details about the pattern).

Acceptable Values

[path]The path to file that contains additional rules for settings validation.

Example Usage

The following configuration points to the settings in the new_setting_rules.properties file:

settings.rules.file.dottest=C:\\parasoft\\jtest\\new_setting_rules.properties

The settings included in the file may resemble the following:

 engine.path=$ANY
engine.enabled=$BOOLEAN
engine.analysis.deep=$INTEGER
engine.severity.limit=$REGEXP{[1-5]}
engine.verbosity.level=$REGEXP_IC{(low)|(normal)|(high)}

usage.reporting.enabled

This setting enables or disables collecting anonymous usage information and sending it to Parasoft. Read our privacy statement to learn more at https://www.parasoft.com/privacy-policy.

Acceptable Values

trueUsage data is sent to Parasoft.
falseDefault. Usage data is not sent to Parasoft.

Example Usage

The following configuration enables collecting usage data.

usage.reporting.enabled=true


  • No labels

Need assistance? Visit our support page