...
- Choose Parasoft> Preferences from a SOAtest desktop installation and configure your settings.
- Export the settings as a localsettings settings file. The localsettings settings file is a configuration file configuration file with a .properties file extension.
- Add the settings to your team’s DTP server.
- Connect your SOAtest desktops and/or servers to DTP and allow it to automatically configure your SOAtest installations. You can also manually extend or override those settings as needed.
- When team-wide preferences need to be updated, update them on the DTP. Changes will automatically be propagated to the connected tools.
If your organization does not use DTP, you can export the settings configured in one SOAtest installation and import them manually to each desktop installation. For server configurations, use the following command to point to a locally-stored .properties file:
-localsettings settings <path/to/file>
Configuring Preferences in the UI
- Choose Parasoft> Preferences and configure the following settings:
- E-mail, see Configuring Email Settings.
- License, see Licensing.
- DTP, see Connecting to DTP.
- Team Server (deprecated), see Connecting to Parasoft Team Server.
- Source control, see Connecting to Your Source Control Repository.
- Authors, see Specifying Author-to-Author and Author-to-Email Mappings.
- Any additional settings you want to share. See Preference Configuration Basics for details.
- Click Parasoft in the sidebar menu to return to the top-level preferences page and click the Share link.
Specify where you want to store the localsettings settings file and which settings you want to include in the exported file.
Copy the contents of the .properties file to the project or global settings in DTP. See the DTP documentation for details.
...
You can specify the preference settings stored in a file or allow DTP to auto-configure your settings.
| Anchor | ||||
|---|---|---|---|---|
|
...
Stored Settings File
For SOAtest server installations, use the following command to point to a locally - stored localsettings settings file:
-localsettings settings <path/to/file>
See Configuring LocalsettingsSettings for details on manually configuring the localsettings settings file.
Using the Settings Stored on DTP
...
| Code Block | ||
|---|---|---|
| ||
-dtp.autoconfig [email protected]:8080 |
If you already have a localsettings settings file and want to import additional settings from DTP, use the dtp.autoconfig=true option and specify your connection settings. For example:
...
You can define common properties in DTP and configure per-test-run specific properties in various localsettings settings files for different test runs.
...
You can configure several localsettings settings files if you want to use a combination of settings. This enables you to use, for example, core project settings stored on DTP, test-specific settings associated with the particular machine, and custom settings for a specific set of analyses.
- Export each group of settings as a localsettings settings file using the procedure described in Exporting GUI Preferences to a localsettings settings File
Use both
-dtp.autoconfigand-localsettingssettingsat the command line. For example:Code Block language powershell -dtp.autoconfig [email protected]:8080 -localsettingssettings machine_override_properties -localsettingssettings project_override_properties
Specify the most general settings first and your most specific settings last. Settings will be processed in the order in which they are listed; any settings that are duplicated across groups will be overridden each time a duplicate is found.
...
Parasoft (Root-Level) | Sets general preferences and allows you to export settings to a localsettings settings file.
|
|---|---|
| Authors | Maps a team member’s automatically-detected username to a different username and/or email address. See Configuring Task Assignment and Code Authorship Settings. |
| Browser | Specifies which browser executables to use for web testing. See Browser Settings. |
| Configurations | Specifies the number of Test Configurations available in the Parasoft> Test History menu, the location where custom static analysis rules (user rules) are saved and searched for, and the location where user-defined Test Configurations and rules are saved and searched for.
|
| Console | Specifies settings for the Console view.
|
| Continuous Testing Platform | Configures your connection to Continuous Testing Platform. See Continuous Testing Platform. Contact your Parasoft representative for additional information. |
| DTP | Configures your connection to DTP. See Connecting to DTP. |
| Dictionary | Configures the language dictionary. |
Specifies email settings used for report notifications and for sending files to Parasoft Technical Support. | |
| Global Data Sources | Specifies where the datasources.properties file is saved. See Adding a Data Source at the Test Suite, Project, or Global Level. |
| Issue Tracking Tags | Specifies custom tags that the team uses to associate a test case with an issue from an issue/feature/defect tracking system (for example, Jira). |
| JDBC Drivers | Specifies JDBC drivers that are needed to connect to a database. |
| License | Specifies license settings. See Licensing. |
| MIME Types | Specifies recognized MIME types. |
| Misc. | Enables you to specify the following settings:
|
| Proxy | Specifies custom proxy settings. The IDE proxy settings (General> Network) are used by default. |
| Quality Tasks | Specifies general options related to how tasks are displayed in the Quality Tasks view. |
| Reports | Specifies what reports include and how they are formatted. The value used for the Session Tag field cannot contain colon characters (:). |
| Scanning | Specifies default user agent, FTP log, and script extensions. |
| Scope and Authorship | Specifies how code authorship is computed and how tasks are assigned to different team members. See Configuring Task Assignment and Code Authorship Settings |
| Scripting | Specifies additional scripting languages you can use in Scripting Tools. See Extensibility or Scripting Basics. |
| Security | Specifies settings for allowing the tool to connect to secure applications. See Configuring for Services Deployed Over HTTPS |
| Server | Specifies SOAtest server start-up and port settings. See Parasoft Virtualize Server WAR File Deployment. |
| SOAP | Specifies default SOAP settings. |
| Source Controls | Specifies the connection to your source control repositories. |
| System Properties | Specifies additional JARs and class folders to add to the classpath. |
| Technical Support | Specifies options for preparing "support archives" and sending them to the Parasoft support team. See カスタマーサポート |
| UDDI | Specifies UDDI inquiry endpoint. |
| WSDL History | Enables you to set/reset the WSDL history. |
| XML Conversion | Specifies data model directories for XML conversion. |
| XML Schema History | Enables you to set/reset the XML schema history. |
| XML Schema Locations | Enables you to set/reset XML schema namespaces. |
...
Some preferences, such as the report settings, enable you to use variables. This enables you to dynamically define outputs, such as report names or report metadata. See Configuring LocalsettingsSettings for additional information about variables.
...