This section provides information about the Jtest goals for Maven and their parameters. The following goals are available:
Full name: com.parasoft.jtest:jtest-maven-plugin:1.2.13:jtest This goal should be used as a Maven report. It collects the build data and executes Jtest with the configured parameters (see Configuring the Jtest Plugin for Maven). It is called at the end of the build session and collects the aggregated data of every project. The goal works as an aggregator, which means it is not tied to a build lifecycle phase. It can be executed as a build plugin or as a reporting plugin (the Attributes
Parameters
Parameter Details
|
We recommend using this parameter with the "clean" goal to prevent the Jtest Plugin from importing test results from previous executions. |
jtest.forceTestReportsImport
Jtest installation directory.
jtest.home
A list of ignored compilation IDs. Supported by Maven since 3.0.3.
jtest.ignoredids
Specifies 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/**
jtest.include
A list of include parameters. Can be configured by property since Maven 3.0.3.
jtest.includes
The project name template. By default, the following pattern is used to create project names in json: :"groupId:artifactId ". This parameter allows you to configure the pattern with the options [groupId], [artifactId], [version] and [basedir], for example, to make a project name compatible with the project name in Eclipse.
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. |
jtest.projectNameTemplate
Enables reporting results of local analysis to the DTP server.
jtest.publish
Specifies the directory where the report will be created. By dafault it is ${project.build.directory}/jtest
. This parameter is ignored when Jtest is used as a reporting plugin (see Configuring the Jtest Plugin for Maven as a Reporting Plugin). In such case, the report is appended to the site
in Project Reports section, and the report property points to the ${project.build.directory}/site
directory.
jtest.report
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:
The Jtest Plugin for Maven resolves
${ProjectName}
to ${artifactId}:${groupId}
.
jtest.resource
A list of resource parameters. Can be configured by property since Maven 3.0.3.
jtest.resources
An absolute or relative path to the *properties file that includes custom configuration settings.
Some of the setting names may not be consistent with the settings dedicated for the build system plugins. See Configuration Settings for details. |
jtest.settings
A list of settings parameters. Supported by Maven since 3.0.3. Can be configured by property since Maven 3.0.3.
jtest.settingsList
Displays detailed progress information.
Prints the current settings and customizations along with the information where each of them is configured (e.g. in the jtest.properties file).
jtest.showsettings
Allows you to skip the Jtest execution phase. If set to true
, only the jtest.data.json data file is generated.
jtest.skip
Full name: com.parasoft.jtest:jtest-maven-plugin:1.2.13:agent This goal generates the Jtest Agent settings based on the build modules, and sets the javaagent VM agument in the properties specified with the agentPropertyNames parameter. By default, it tries to inject
Attributes
Required Parameters
Optional Parameters
Parameter Details
|
Full name: com.parasoft.jtest:jtest-maven-plugin:1.2.13:monitor This goal should be used as a Maven report. It scans the build to generate settings for the Jtest Java Agent, and creates a monitor package in location specified with the monitorLocation parameter. The monitor package contains the following:
Attributes
Optional Parameters
Parameter Details
|
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. |
Enables reporting results of local analysis to the DTP server.
jtest.publish
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:
The Jtest Plugin for Maven resolves
${ProjectName}
to ${artifactId}:${groupId}
.
jtest.resource
A list of resource parameters. Can be configured by property since Maven 3.0.3.
jtest.resources
An absolute or relative path to the *properties file that includes custom configuration settings.
Some of the setting names may not be consistent with the settings dedicated for the build system plugins. See Configuration Settings for details. |
jtest.settings
A list of settings parameters. Supported by Maven since 3.0.3. Can be configured by property since Maven 3.0.3.
jtest.settingsList
Displays detailed progress information.
Prints the current settings and customizations along with the information where each of them is configured (e.g. in the jtest.properties file).
jtest.showsettings
Allows you to skip the Jtest execution phase. If set to true
, only the jtest.data.json data file is generated.
jtest.skip
This goal is provided by the test impact analysis plugin shipped with Jtest and allows you to perform test impact analysis of your project (see Test Impact Analysis). Required Parameters
|
Name | User Property | Accepted values / data type | Description |
---|---|---|---|
runFailingTests | parasoft.runFailingTests | true | false | Enables including all failed tests form the previous run in the current test run, even if they were not affected by the changes. The default is: |
runModifiedTests | parasoft.runModifiedTests | true | false | Enables including both modified and new tests in the test run. The default is: |
settingsFiles | jtest.settings | Path | The path to the .properties file that includes custom configuration settings. You can use a comma-separated list to provide multiple files that will be merged before execution. The settings configured in the jtest.properties file located in the Jtest installation directory are automatically included. |
Full name: com.parasoft.jtest:jtest-maven-plugin:1.2.13:instrument This goal instuments the compiled application and test classes to collect coverage information.
Attributes
Required Parameters
Optional Parameters
Parameter Details
|