...
You can also create a custom .properties file and pass it to the jtestcliwith 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.
| Code Block |
|---|
jtestcli -settings path/to/settings.properties -settings path/to/another/settings.properties |
| Info | ||
|---|---|---|
| ||
Use double backslashes to specify file paths in the .properties file on Windows. For example:
|
| Info | ||
|---|---|---|
| ||
We highly recommend that you use encoded passwords to ensure successful authentication and increase the level of security; see Creating an Encoded Password. |
Settings Hierarchy
General settings are applied in the following order:
[INSTALL_DIR]/etc/jtestcli.properties: the base configuration file that should not be modified.[INSTALL_DIR]/jtestcli.properties: the main configuration file you can use to specify your settings; it contains a list of basic configuration settings (license, reporting, etc.) you need to uncomment before configuring the setting's value.[USER_HOME_DIR]/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 re installations or updates).[WORKING_DIR]/jtestcli.properties: for your convenience, you can store the configuration file in your working directory.- Custom settings passed with the command line switch
-settings path/to/settings.properties(e.g.,-settings ../settings.properties). - Custom settings passed with the command line switch
-property [key=value](e.g.-property "report.mail.enabled=true").
All of the above settings can be overridden by settings that are passed with command line switches, such as -report, -config, etc.
Ant and Maven Pattern
You can provide the path to the settings file with Ant or Maven using the following pattern:
...