Versions Compared

Old Version 3

changes.mady.by.user Robert Andelin

Saved on

compared with

New Version 4

changes.mady.by.user Chieko Sugizaki

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2021.1

...

  1. Choose Parasoft> Preferences from a SOAtest desktop installation and configure your settings. 
  2. Export the settings as a settings localsettings file. The settings localsettings file is a configuration file configuration file with a .properties file extension. 
  3. Add the settings to your team’s DTP server.
  4. 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.
  5. 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 localsettings <path/to/file> 

Configuring Preferences in the UI

  1. Choose Parasoft> Preferences and configure the following settings:
  2. Click Parasoft in the sidebar menu to return to the top-level preferences page and click the Share link.

  3. Specify where you want to store the settings localsettings file and which settings you want to include in the exported file.



  4. 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
Using an Existing Locally-Stored Localsettings File
Using an Existing Locally-Stored Localsettings File
Using an Existing

...

Locally

...

-stored Localsettings File

For SOAtest server installations, use the following command to point to a locally-stored settings localsettings file:

-settings localsettings <path/to/file>

See Configuring SettingsLocalsettings for details on manually configuring the settings localsettings file.

Using the Settings Stored on DTP

...

Code Block
languagepowershell
-dtp.autoconfig [email protected]:8080

If you already have a settings localsettings file and want to import additional settings from DTP, use the dtp.autoconfig=true option and specify your connection settings. For example: 

Code Block
languagetext
dtp.enabled=true
dtp.password=password
dtp.port=8443
dtp.project=projectname
dtp.urlserver=https://host.domain.com:8443
dtp.user=username
dtp.autoconfig=true

You can define common properties in DTP and configure per-test-run specific properties in various settings localsettings files for different test runs.

...

You can configure several settings localsettings 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.

  1. Export each group of settings as a settings localsettings file using the procedure described in Exporting GUI Preferences to a settings localsettings File

  2. Use both -dtp.autoconfig  and -settingslocalsettings at the command line. For example:

    Code Block
    languagepowershell
    -dtp.autoconfig [email protected]:8080 -settingslocalsettings machine_override_properties -settingslocalsettings 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 settings localsettings file.

    • Ignore solution and solution folder names in paths: Enables "reduced paths" mode. In this mode—where Parasoft Test uses only reduced (project relative) paths. Names of solution and solution folders will be skipped in these paths. New paths will be unique because project names are unique inside a solution.
    • User name: Allows you to set a different user name than the one specified in the operating system. The user name is used in several Parasoft interfaces.
    • Share/import: See Exporting GUI Preferences to a settings localsettings File.
    • Send anonymous usage data to Parasoft: Allows you to enable or disable collecting and sending usage data to Parasoft. Read our privacy statement to learn more at https://www.parasoft.com/privacy-policy.
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.

BrowserSpecifies 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.

    • Size of recently run test configurations: Determines the number of Test Configurations available in the Parasoft> Test History menu.
    • Custom directories: Indicates where user-defined Test Configurations and  custom directories (e.g., for user rules, embedded cross-compilers, etc.) are saved.
    • Run configuration on save: Tells the product to automatically run the specified Test Configuration each time a source file is saved. This enables fully-automated continuous desktop analysis.
Console

Specifies settings for the Console view.

    • Low: Configures the Console view to show errors and basic information about the current step’s name and status (done, failed, up-to-date).
    • Normal: Adds command lines and issues reported during test and analysis.
    • High: Uses full-format violation listings and also reports warnings.
    • Show console on any change: Determines whether the console is brought to the front any time its content changes
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.

DictionaryConfigures the language dictionary.
E-mail

Specifies email settings used for report notifications and for sending files to Parasoft Technical Support.

See Configuring Email Settings.

Global Data SourcesSpecifies 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). 

See Using Custom Defect/Issue Tracking Tags

JDBC Drivers

Specifies JDBC drivers that are needed to connect to a database. 

 See  Configuring JDBC Drivers

License

Specifies license settings.

See Licensing.

MIME TypesSpecifies recognized MIME types.
Misc.

Enables you to specify the following settings:

  • Enable/disable tool descriptions in Add Test and Add Output Wizards
  • Enable auto-beautify (formatting) for tools
  • Character encoding
  • Default timeout for connections
  • Duplicate error handling
  • Reset cookies for HTTP sessions
  • Import preferences from a binary file
  • Save settings
  • Automatic backups
ProxySpecifies 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.

See Configuring Task Reporting Preferences

Reports

Specifies what reports include and how they are formatted. The value used for the Session Tag field cannot contain colon characters (:).

See Configuring Reporting Settings 

ScanningSpecifies 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

ScriptingSpecifies additional scripting languages you can use in Scripting Tools. See Extensibility or Scripting Basics.
SecuritySpecifies settings for allowing the tool to connect to secure applications. See Configuring for Services Deployed Over HTTPS
ServerSpecifies SOAtest server start-up and port settings. See Parasoft Virtualize Server WAR File Deployment.
SOAPSpecifies default SOAP settings.
Source Controls

Specifies the connection to your source control repositories. 

See Connecting to Your Source Control Repository

System PropertiesSpecifies 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 カスタマーサポート

UDDISpecifies UDDI inquiry endpoint.
WSDL HistoryEnables you to set/reset the WSDL history.
XML ConversionSpecifies data model directories for XML conversion.
XML Schema HistoryEnables you to set/reset the XML schema history.
XML Schema LocationsEnables 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 SettingsLocalsettings for additional information about variables.

...