Page History

Sets general preferences and allows you to export settings to a 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 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.

Maps a team member’s automatically-detected username to a different username and/or email address. See Configuring Task Assignment and Code Authorship Settings.

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.

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

Configures your connection to DTP.

See Connecting to DTP.

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

See Configuring Email Settings.

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

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

 See  Configuring JDBC Drivers

Specifies license settings.

See Licensing.

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

Specifies general options related to how tasks are displayed in the Quality Tasks view.

See Configuring Task Reporting Preferences

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 

Specifies how code authorship is computed and how tasks are assigned to different team members. 

See Configuring Task Assignment and Code Authorship Settings

Specifies the connection to your source control repositories. 

See Connecting to Your Source Control Repository

Specifies options for preparing "support archives" and sending them to the Parasoft support team.

See カスタマーサポート