Page tree

Skip to end of metadata
Go to start of metadata

You can filter the data associated with your projects by setting the project definitions and Parasoft Test settings. This enables you to associate your project with a source code management system, bug tracking system, or with tools that run automatic tests.

  1. Open an existing project (see Opening Existing Projects).
  2. Click the Project Definitions tab to set filters (see Project Definitions).
  3. Click the Parasoft Test Settings tab to connect DTP to Parasoft code analysis tools (see Parasoft Test Settings).
  4. Click Save

The following sections provide more information about project configuration settings and how to set them.

Project Definitions

Project definitions are associated with the Project Center module of DTP. See the Project Center documentation for details.

Parasoft Test Settings

Specify the settings that connected DTP Engines should use when analyzing and testing code associated with the project in the Parasoft Test Settings tab. When engines are connected to DTP, they imports and uses these settings, which enables you to centrally configure DTP Engine execution properties. The settings specified in the engine's .properties file, however, take precedence over the settings configure in this tab. See the DTP Engine documentation for details on available settings. 

You can also configure the Parasoft Test Settings for all projects. See Connecting Parasoft Test

Example Settings

#License Settings
#Mail Settings

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 property. For example:

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

Auto-configuring DTP Engines

Parasoft Test Settings can be used to 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:

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:


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

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