...
Click Parasoft in the menu bar and choose
Conditional Content product: (jtest) product: (jtest) sv-attr:0A01020401598D973E6641760F8AF4E5 0A01020401598D973E671AAA268425A3 Preferences (Eclipse), Options (NetBeans) or Settings (IntelliJ). Then select Configuration.
Right-click the test configuration you want to duplicate, then choose Duplicate Locally.
The configuration will be added to the User directory and nested in a parent directory matching the source.
Right-click the duplicate configuration and choose Edit to open the Test Configuration Editor in you browser.
NOTE: The Test Configuration Editor is handled by a separate web server process and may be blocked if a strict firewall is installed on your machine. In such case, allow the process to run when prompted.
Choosing Edit as text opens a textual representation of the configuration in a simple configuration editor (deprecated).
- Click a tab to access a group of related test configuration settings. For additional information about test configuration settings, mouse over an information icon ("i") next to a configuration setting. The following tabs are available:
Table of Contents maxLevel 2 minLevel 2
...
The Scope tab contains a set of filters that you can configure to define the parts of the code that the test configuration should cover. You must connect the DTP Engine the Jtest to source control in order to collect scope information. Click Save to preserve any changes you make on this tab.
...
Expand the Time filters settings to set time-based filters at the file or line level. The time filters enable you to restrict the scope of analysis to a specific date range or period. If the scope.scontrol setting is set to true and the source control settings for the DTP Engine for Jtest are configured, the modification time is set from the source control history. If scope.local is set to true, then the modification time is set form the file system of the machine running the DTP engineanalysis.
You can configure the following settings:
...
| Check all files | Default. Enable this option to include all files in the scope of the analysis the user has access to. |
|---|---|
| Check locally-modified files | Enable this option to check only locally-modified files. Files in the source control system will be excluded. The following DTP Engine setting must be configured for this option to take effect:
|
| Check files modified within a date range | Enable this option and specify a date range to include in the scope. Files that were modified or added within the specified range will be checked. |
| Check files modified witin last n days | Enable this option and specify the number of days to include in the scope. Files that were modified or added within the specified number of days will be checked. |
| Check files modified between the current branch and the specified branch | Enable this option to specify a range of branches to include in the scope. Files that were modified from the user's current branch to the specified branch will be checked. Files that did not change between branches are excluded. You can enable the following options:
|
...
| Check all lines | Default. Enable this option to include all lines of code in the scope of the analysis the user has access to. |
|---|---|
| Check locally-modified lines | Enable this option to check only locally-modified lines of code. Lines of code in the source control system will be excluded. The following DTP Engine setting must be configured for this option to take effect:
|
| Check lines modified since | Enable this option and specify a cut-off date to include in the scope. Lines of code that were modified or added within the specified range will be checked. |
| Check lines modified witin last n days | Enable this option and specify the number of days to include in the scope. Lines of code that were modified or added within the specified number of days will be checked. |
...
Expand the Author filters section to limit the scope of analysis to specific authors. If the scope.scontrol setting is set to true and the source control settings of the DTP Engines are configured, then file authorship is taken from the source control system. If the scope.xmlmap is set to true and the XML map settings are configured for the DTP Engines, then files authorship is taken from the map.
...
Click the Static Analysis tab, and enable or disable the Enable static analysis checkbox to enable/disable static and flow analysis. Click Save to preserve any changes you make on this tab.
...
Advanced Settings
Expand the Advanced Settings section to enable the following options:
...
- Set an upper limit on the number of violations that can be reported for each rule.
- Enable/disable suppressions configured on the engine host.
Conditional Content product: (jtest) product: (jtest) sv-attr:0A01020401598D973E6641760F8AF4E5 0A01020401598D973E671AAA268425A3Engine host. Enable the Skip global analysis option to prevent the collection and use of global data
...
Flow Analysis Advanced Settings
...
See Configuring Flow Analysis for details.
...
...
Inversion of Control Framework Settings
Expand the Inversion of Control Framework Settings section to specify annotations used for injecting/initialization values during runtime. Enter a comma-separated list of fully qualified names to use as annotations.
Static Analysis - Rules Tab
Click the Static Analysis - Rules tab to enable/disable the static analysis rules the configuration uses. This page shows all the supported rules supported by the DTP Engine. Click Save to preserve any changes you make on this tab.
...
Enable the Show Enabled Only option to only show the enabled rules.
| Anchor | ||||
|---|---|---|---|---|
|
The Local Rule Map Applied field displays the path to the folder that contains the rule mapping file. The rulemap.xml file available in the displayed location is applied to all local test configurations (see Specifying the Custom Rule and Mapping Directory for details).
...
Click Parasoft in the menu bar and choose
Conditional Content product: (jtest) product: (jtest) sv-attr:0A01020401598D973E6641760F8AF4E5 0A01020401598D973E671AAA268425A3 Preferences (Eclipse), Options (NetBeans) or Settings (IntelliJ).
Then select Configuration.
Right-click the Built-in or User test configuration you want to duplicate, then choose Duplicate on DTP.
The configuration will be added to the DTP directory and uploaded to the DTP server (see Connecting to DTP Server との接続)
- Right-click the duplicate configuration and choose Edit.
If you are not logged in DTP, the DTP login page will open in a browser. Provide your credentials to log in.
The Test Configuration page in DTP will open. - Open the list of test configurations. The duplicated test configuration will be available in the configurations lists.
- Click the duplicated test configuration to open the configuration interface. See the DTP documentation for details about how to customize test configurations on DTP.
...