Page tree

Skip to end of metadata
Go to start of metadata

In this section:

Configuring the Settings

Jtest  can be configured with settings (see Configuration Settings) that should be specified in a .properties file. The basic settings are listed in the jtestcli.properties  file shipped in [INSTALL_DIR]. 

For your convenience, you can also store common settings in a jtestcli.properties file in the $USER_HOME directory to overwrite settings stored in the properties file in the [INSTALL_DIR] directory. You can also create a custom .properties file and pass it to thejtestcliwith the -settings switch. Use absolute paths to specify the custom .properties file. You can use the -settings switch multiple times to specify several .properties files. Entries with the same key will be overwritten.

jtestcli -settings path/to/settings.properties  -settings path/to/another/settings.properties

File path convention on Windows

Use double backslashes to specify file paths in the .properties file on Windows. For example:

configuration.dir.user=C:\\parasoft\\2018\\configs\\user


Settings Hierarchy

General settings are applied in the following order: 

  1. [INSTALL_DIR]/etc/jtestcli.properties: the base configuration file that should not be modified.
  2. [INSTALL_DIR]/jtestcli.properties: the main configuration file you can use to specify your settings that map contains templates for commonly used settings (license, reporting etc.).
  3. [USER_HOME]/jtestcli.properties: for your convenience, you can store the configuration file in your home directory to overwrite settings from the [INSTALL_DIR] (for example, to ensure your settings are not affected by reinstallations or updates).
  4. [WORKING_DIR]/jtestcli.properties: for your convenience, you can store the configuration file in your working directory.
  5. Custom settings passed with the command line switch -settings path/to/settings.properties (e.g., -settings ../settings.properties).
  6. Custom settings passed with the command line switch -property [key=value].
All of the above settings can be overridden by custom settings that are passed with command line switches (e.g. -report, -config).

Ant and Maven Pattern

You can provide the path to the settings file with Ant or Maven using the following pattern:

<settings>path/to/settings.properties</settings>

Settings Hierarchy for Maven

If you use Maven, you can configure jtestcli settings with:

  • -Djtest.[Maven property name] (e.g., -Djtest.settings="my.general.properties").
  • the pom.xml file
  • -Dproperty.jtest.[property name] (e.g., -Dproperty.jtest.license.use_network=true)

Both -Djtest and pom.xml override settings that are passed with -Dproperty.jtest.

-Djtest overrides settings in pom.xml if they are provided as Maven properties. However, if a setting value is specified directly in pom.xml, it has the highest priority and cannot be overridden by command line settings. For example, the test configuration specified in pom.xml as a user property <config>${jtest.config}</config> can be overridden with -Djtest.config. If it is hardcoded as <config>builtin://Demo Configuration</config>, it cannot be overridden.

See Jtest Goals Reference for Maven for the complete list of parameters.

It is recommended that you keep all user-level customizations, including custom settings, license, rules, test configurations, compiler configurations, outside of the Jtest installation directory so they are not affected by reinstallations or updates.

Viewing Current Settings 

Use the -showsettings option to print the current settings and customizations, including the origin file for each configuration. 

Ant and Maven Pattern

If you use Ant or Maven, you can use the following pattern to view the current settings:

<showsettings>true</showsettings>

Auto-configuring Settings from DTP Server

You can specify settings in DTP and configure your Parasoft tool to use the settings when it connects to DTP Server. This enables you to use the same settings across multiple machines and configurations to ensure consistency. Edit the following setting in the .properties file to enable auto-configuration:  

dtp.autoconfig=true

Settings can be auto-configured for the entire organization or per project. 

Specifying Organization-wide Settings

  1. Log into DTP with administrator credentials 
  2. Switch to Report Center and choose Report Center Settings from the menu.

  3.  Go to Additional Settings> Report Center Administration.
  4. Choose Settings> Parasoft Test Global Settings and enter the settings from the .properties file.
  5. Click Save.

Specifying Settings Per Project

  1. Log into DTP with administrator credentials
  2. Switch to Report Center and choose Report Center Settings from the menu.
  3. Choose Projects> Search and click Search.
  4. Click on your project name in the results and click the Parasoft Test Settings tab
  5. Enter the settings from the .properties and click Save.

JVM, Framework, and Application Setup

The following table describes additional configuration files for setting up Jtest.

FileDescriptionDirectory
jtestcli.propertiesContains the default settings for the Jtest properties.[INSTALL_DIR]
jtestcli.jvmContains JVM arguments that the jtestcli.exe (jtestcli) executable will use when starting Java processes.[INSTALL_DIR]/etc
framework.propertiesContains properties that are passed to the launched Felix OSGI framework. There is typically no need to edit this file.[INSTALL_DIR]/etc
formatting.propertiesContains formatting rules for the default Jtest properties.[INSTALL_DIR]/etc
logging.xmlLogger configuration file; outputs a silent console by default and warn level on the jtest.log file.[INSTALL_DIR]/etc
logging.console.debug.xmlLogger configuration with debug level on the console output.[INSTALL_DIR]/etc

  • No labels