In this section:

About Test Settings

You can configure project-specific settings for test and code analysis tools, such as Parasoft DTP Engines, SOAtest, and C++test Desktop. When tools are connected to DTP, they import and use these settings, which enables you to centrally configure DTP Engine execution properties. The settings specified in the tool's .properties file, however, take precedence over the settings configure in this section. See the specific tool documentation for details on available settings.  

  1. Choose Report Center Settings from the settings menu.
  2. Click Projects in the Administration tab and click on a project. 
  3. Enter your settings in the Parasoft Test Settings section. Enter each setting on a new line. Use the # character to add comments.

     

    You can also click the information icon in the label for additional information and to view example settings.

You can also configure the settings for all projects. See Configuring Parasoft Test for All Projects

Example Settings

#License Settings
license.network.host=dtp.company.com
license.network.port=2222
license.use_network=true
#Mail Settings
report.mail.domain=company.com
report.mail.from=john.doe
report.mail.password=123456789
report.mail.server=mail.company.com
report.mail.username=john

About File Encoding

By default, DTP assumes that source code is encoded in UTF-8. If the source code is encoded with a different character set, you can specify it in the Parasoft Test Settings form by adding the file.encoding.name property. For example:

file.encoding.name=UTF-16

You can configure this setting for individual projects or for all projects if all source code is encoded in the same way. See Configuring Parasoft Test for All Projects for additional information.

Auto-configuring DTP Engines

You can automatically configure DTP Engines that have the dtp.autoconfig property set to true. This enables you to set many settings that can be reused by both DTP and DTP Engines. See "Development Testing Platform Settings" in the DTP Engines documentation. 

For example, the following settings would be added to the DTP Engine configuration file:

dtp.autoconfig=true
scontrol.svn.exec=C\:\\Program Files\\svn\\bin\\svn.exe

This would enable the engine to use the following example configurations set in the Parasoft Test Global Settings field:

scontrol.svn.exec=/usr/bin/svn
scontrol.rep1.type=svn
scontrol.rep1.svn.url=http\://foo.bar.com/svn/repos
scontrol.rep1.svn.login=foo
scontrol.rep1.svn.password=65707c


Displaying Source Code from Source Control System
In some cases, settings reused by DTP Engines and DTP Server require further customization. For instance, DTP Server may require different Source Control Server credentials than DTP Engine.

Auto-configuration can still be used by adding the server. prefix to identify the setting as a DTP Server-only setting. In the following Parasoft Test Settings, the SVN executable directory is specified for DTP Engines with the scontrol.svn.exec setting, but for DTP Server the directory is set with server.scontrol.svn.exec:

scontrol.svn.exec=C\:\\Program Files\\svn\\bin\\svn.exe
server.scontrol.svn.exec=/usr/bin/svn
scontrol.rep1.type=svn
scontrol.rep1.svn.url=http\://foo.bar.com/svn/repos
scontrol.rep1.svn.login=foo
scontrol.rep1.svn.password=65707c
server.scontrol.rep1.svn.login=bar
server.scontrol.rep1.svn.password=19787a

DTP Server always prioritizes the value of setting with server. prefix if the same non-prefixed also appears in the same Parasoft Test view.

The following precedence of overwriting settings is used in DTP Server when the same setting appears in Parasoft Test Global Settings and project-specific Parasoft Test settings:

  • Project specific Parasoft Test Settings with server. prefix
  • Project specific Parasoft Test Settings without server. prefix
  • Parasoft Test Global Settings with server. prefix
  • Parasoft Test Global Settings without server. prefix

  • No labels