Parasoft Jtest DTP Engine 10.3.3
Page tree

Versions Compared

Old Version 6

changes.mady.by.user Hiromi Takahashi

Saved on

compared with

New Version Current

changes.mady.by.user Anna Stuchlik

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
maxLevel1

Configuring the Settings

...

Jtest

...

Jtest DTP Engine 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]. 

Conditional Content
product: (jtest)
product: (jtest)
sv-attr:0A01020401598D973E6641760F8AF4E50A01020401598D973E671AAA268425A3

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 the 

...

jtestcli

the jtestcli with the -settings switch. 

...

You can use the -settings switch multiple times to specify several .properties files. Entries with the same key will be overwritten.

...

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

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.

    Conditional Contentproduct: (jtest)product: (jtest)sv-attr:0A01020401598D973E6641760F8AF4E5

    0A01020401598D973E671AAA268425A3

  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.).

    Conditional Contentproduct: (jtest)product: (jtest)sv-attr:0A01020401598D973E6641760F8AF4E50A01020401598D973E671AAA268425A3

  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).

    Conditional Contentproduct: (jtest)product: (jtest)sv-attr:0A01020401598D973E6641760F8AF4E50A01020401598D973E671AAA268425A3

  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)

    Conditional Contentproduct: (cpptest, jtest)product: (cpptest, jtest)sv-attr:0A01020401598D973E6641760F8AF4E50A01020401598D973E6749C5267CE6FE 0A01020401598D973E671AAA268425A36.

    .

  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).

Conditional Content
product: (jtest)
product: (jtest)
sv-attr:0A01020401598D973E6641760F8AF4E50A01020401598D973E671AAA268425A3

Ant and Maven Pattern

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

Code Block
<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 user 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>, itcannot be overridden.

See the Jtest Goal page in plugins-manual.html 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 

...

Conditional Content
product: (jtest)
product: (jtest)
sv-attr:0A01020401598D973E6641760F8AF4E50A01020401598D973E671AAA268425A3

Ant and Maven Pattern

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

Code Block
<showsettings>true</showsettings>



Conditional Content
product: (jtest)
product: (jtest)
sv-attr:0A01020401598D973E6641760F8AF4E50A01020401598D973E671AAA268425A3

JVM, Framework, and Application Setup

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

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