The Gradle task to execute Jtest. AttributesName | Accepted values / data type | Description | Required |
---|
compilation | Compilation | A description of manual configuration data (see Manual Customization of Compilation Data) | No | compilations | List | A list of descriptions of manual configuration data (see Manual Customization of Compilation Data) | No | dataUpdate | String | Allows you to manually update compilation data collected from the build. User property is: jtest.dataUpdate | No | config | String | The name of a built-in, DTP, or user-defined test configuration. User property is: jtest.config | No | exclude | String | Specifies a subset of files or packages from the selected resources that will be excluded from analysis. You can provide the qualified names or use Ant glob patterns to match more filenames. User property is: jtest.exclude | No | excludes | List | A list of exclude parameters. User property is: jtest.excludes | No | excludeTestSources | true | false | Anchor |
---|
| excludeTestSources |
---|
| excludeTestSources |
---|
|
Excludes test source code from analysis. User property is: jtest.excludeTestSources . | No | fail | true | false | Fails the build if any violation is reported. User property is: jtest.fail | No | home | Path | Specifies the Jtest installation directory. If not defined, the Jtest location specified on PATH will be used. User property is: jtest.home | Recommended | ignoredIds | List | A list of ignored compilation IDs. User property is: jtest.ignoredids | No | include | String | Specifies a subset of files or packages form the selected resources that will be included during analysis. User property is: jtest.include | No | includes | List | A list of include parameters. User property is: jtest.includes | No | publish | true | false | Enables reporting results of local analysis to the DTP server. User property is: jtest.publish | No | report | Path | Specifies the directory where the report will be created. User property is: jtest.report | No | resource | String | Specifies the input scope for analysis. If no resources are specified, Jtest will analyze resources from every built project. User property is: jtest.resource | No | resources | List | A list of resource parameters. User property is: jtest.resources | No | settings | Path | An absolute or relative path to the *properties file that includes custom configuration settings. User property is: jtest.settings | No | settingsList | List | A list of settings parameters. User property is: jtest.settingsList | No | showDetails | true | false | Displays detailed progress information. User property is: jtest.showdetails | No | showSettings | true | false | Prints the current settings and customizations along with the information where each of them is configured (e.g. in the jtest.properties file). User property is: jtest.showsettings | No | projectNameTemplate | String | The project name template. This parameter allows you to configure the pattern with the options [group], [name], [version], [path], and [basedir]. User property is: jtest.projectNameTemplate | No | skip | true | false | Allows you to skip the Jtest execution phase. If set to true , only the jtest.data.json data file is generated. User property is: jtest.skip | No |
Parameter DetailsconfigThe name of a test configuration. The following configuration types are supported: - built-in test configurations, for example
"builtin://Recommended Rules" - dtp test configurations, for example
"dtp://New Config" - user-defined test configurations, for example
"user://Your Config"
User-defined test configurations should be stored in the [INSTALL_DIR]/configs/user directory as *.properties files.
dataUpdateAllows you to manually update compilation data collected from the build. - Supported actions: prepend, append, and set.
- Supported data types: classpath, bootpath, sourcepath, binarypath, sourcecode (set only) and encoding (set only)
- Scope: all collected projects data will be updated
See Manual Customization of Compilation Data and Compilation Data Model for more information. excludeSpecifies a subset of files or packages from the selected resources that will be excluded from analysis. You can provide the qualified names. You can use glob patterns to match more filenames. Example 1: The following pattern excludes all files from com.parasoft package and its sub-packages: /com/parasoft/** Example 2: The following pattern excludes all files from the package com.parasoft.jtest, but NOT from its sub-packages: /com/parasoft/jtest/* Example 3: The following pattern excludes all files from the given directory and all subdirectories: path:/home/user/project/src/test/java/** includeSpecifies a subset of files or packages form the selected resources that will be included during analysis. You can use glob patterns to match more filenames. Example 1: The following pattern includes all files from com.parasoft package and its sub-packages: /com/parasoft/** Example 2: The following pattern includes all files from the package com.parasoft.jtest, but NOT from its sub-packages: /com/parasoft/jtest/* Example 3: The following pattern includes all files from the given directory and all subdirectories: path:/home/user/project/src/test/java/** resource
Specifies the input scope for analysis. If no resources are specified, Jtest will analyze resources from every built project. Use the following pattern to specify the paths: ${ProjectName}/my/src/dir/my/package/file.java". You can use the following wildcards: - ? - matches one character
- * - matches zero or more characters, except the path separator (the / character)
- ** - matches entire paths, including the path separator (the / character)
settingsAn absolute or relative path to the *properties file that includes custom configuration settings. Info |
---|
| Some of the setting names may not be consistent with the settings dedicated for the build system plugins. See Configuration Settings for details. |
Anchor |
---|
| projectNameTemplate |
---|
| projectNameTemplate |
---|
| projectNameTemplate
The project name template. By default, the following pattern is used to create project names in json: : "group:name". This parameter allows you to configure the pattern with the options [group], [name], [version], [path], and [basedir], for example, to make a project name compatible with the project name in Eclipse. Warning |
---|
| If you change the pattern for a project that has already been integrated with DTP, DTP will not recognize your project. It will assume that your project after the change of the pattern is a different project. For details, see the DTP documentation. |
Parameter Type DetailsThe following examples assume that the Jtest Plugin for Gradle has been properly configured and applied in the Gradle build script; see Configuring the Jtest Plugin for Gradle. Anchor |
---|
| compilation_type |
---|
| compilation_type |
---|
| Compilation Type- Attribute: Compilation
- A nested object
Code Block |
---|
jtest {
home = "path/to/jtest"
compilation {
id = "main"
override = true
}
} | List Type- Attribute: resources
- Specifies the list of resource patterns to match against resources that are collected during the build.
Code Block |
---|
jtest {
home = "path/to/jtest"
resources = [
"**.java",
"myGradleProjectName/src/com/mycompany/models/**/*.properties"
]
} | String Type- Attribute: Exclude
- Specifies a subset of files or packages from the selected resources that will be excluded from analysis.
Code Block |
---|
jtest {
home = "path/to/jtest"
exclude = "com/mycompany/models/**/NotInteresting*.properties"
} |
See Compilation Data Model for more information. |