...
Jtest can run on either a local or a network license. The license type can be configured in the .properties configuration file in the INSTALL_DIR (or another location; see Configuration Overview for details).
| Note | ||
|---|---|---|
| ||
You must agree to the terms of the Parasoft End User License Agreement (EULA) to use Jtest. The EULA is available in the Jtest installation directory and at https://www.parasoft.com/license. To accept the EULA, enable the following setting in your jtest.properties configuration file:
|
Network License
Typically, the network license is stored in License Server deployed on the same DTP server that you configured for your development testing workflow (see Connecting to DTP 1). This is a "floating" or "machine-locked" license that limits usage to a specified number of machines.
...
desktop_edition: Functionality is optimized for desktop usage.desktop_compliance_edition: Functionality is optimized for desktop usage and configured to support compliance with coding standards.server_edition: Functionality is configured for high-performance usage in server command line mode.server_compliance_edition: Functionality is configured for high-performance usage in server command line mode and includes support for compliance with coding standards.custom_edition: Functionality can be customized. See cpptestjtest.license.custom_edition_features for details.
...
If you are using a local license, you will need your machine ID to request a password from Parasoft. Run the following command from the command line to obtain your machine ID:
| Code Block |
|---|
jtestcli -machineID |
| Info | ||
|---|---|---|
| ||
If you are using Azure or AWS services, you need to configure the
If you set the value to |