Overview
dotTEST 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).
Terms of Parasoft End User License Agreement
You must agree to the terms of the Parasoft End User License Agreement (EULA) to use dotTEST. If you accepted EULA during installation with the dotTEST wizard, the EULA acceptance setting is automatically enabled in the dottestcli.properties configuration file. Otherwise, you need to read the EULA in the dotTEST installation directory or at https://www.parasoft.com/license and manually add the following entry:
parasoft.eula.accepted=true
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). This is a "floating" or "machine-locked" license that limits usage to a specified number of machines.
Network licenses are available in three editions that determine what functionality is available:
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 dottest.license.custom_edition_features for details.
To configure the network license, specify the following settings in the .properties
file:
Set the
dottest.license.use_network
property totrue
.Set the
dottest.license.network.edition
.- Ensure that the connection with DTP is configured; see Connecting to DTP.
Retrieving License from the License Server
You can configure dotTEST to obtain the network license from the License Server (either standalone or deployed on another instance of the DTP server).
Enable the connection by configuring the following setting:
-
dottest.license.use_network=true
Configure the following settings to use a license from the License Server:
- license.network.use.specified.server
=true
- license.network.url=<URL to the License Server>
If authentication is needed:
- license.network.auth.enabled=true
- license.network.user=<username for authentication>
- license.network.password=<password for authentication>
Connecting via OpenID Connect
If OpenID Connect is enabled for the License Server, configure the connection to the OpenID Connect server; see Configuring OpenID Connect.
Local License
To configure the local license, specify the following settings in the .properties
file:
Set the
dottest.license.use_network
property tofalse
.Set the
dottest.license.local.password
property with your password.
Obtaining the Machine ID
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:
dottestcli -machineID
Machine ID for Cloud Environments
If you are using Azure or AWS services, you need to configure the cloudvm
option in the .properties
configuration file to ensure that your machine ID is properly calculated. You can set the option to one of the following values:
azure
- Enables integration with Azureaws
- Enables integration with AWStrue
- Enables integration with the automatically detected cloud computing platformfalse
- Disables integration (the default value)
If you set the value to false
or if the option is not configured, integration with Azure or AWS is disabled.