You can configure SOAtest settings once and propagate them across the team’s installations. You can also extend or override these settings as needed, such as for machine-specific paths.
In this section:
| Table of Contents | ||
|---|---|---|
|
...
Implement the following workflow if your organization uses Parasoft DTP:
- Choose Parasoft> Go to Parasoft > Preferences from a SOAtest desktop installation and configure your settings.
- Export the settings as a settings file. The settings file is a 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:
-settings <path/to/file>
...
- Go to Parasoft > Preferences and configure the following settings:
- E-mail, see Configuring Email Settings.
- License, see Licensing.
- DTP, see Connecting to DTP.
- 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 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 on docs.parasoft.com for details.
| Note | ||
|---|---|---|
| ||
DTP uses multicast DNS to broadcast its services in the local network. This allows SOAtest to automatically detect available DTP servers, which enables easy configuration. In the file <INSTALL>/ eclipse.ini file found in the installation directory, add the line |
Configuring Preferences on Each Installation
...
- Export each group of settings as a settings file using the procedure described in Exporting GUI Preferences to a settings Settings File
Use both
-dtp.autoconfigandautoconfigand-settingsat the command line. For example:Code Block language powershell -dtp.autoconfig [email protected]:8080 -settings machine_override_properties -settings 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.
...
If you are using this recommended process, you can updated update team-wide settings in Parasoft DTP, then those modifications will automatically be propagated to all the connected machines.
To prevent this automated updating (e.g.for example, because you have updated settings locally and do not want them overridden), disable disable Use DTP settings on the Preferences page(s) you do not want updated from DTP.
...
Parasoft (Root-Level) | Sets general preferences and allows you to export settings to a 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> 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. 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. |
...