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:2020.1.0: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. 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.forceTestReportsImportJtest installation directory.
jtest.homeA list of ignored compilation IDs. Supported by Maven since 3.0.3.
jtest.ignoredidsSeocifies 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.includeA list of include parameters. Can be configured by property since Maven 3.0.3.
jtest.includesThe 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.projectNameTemplateEnables reporting results of local analysis to the DTP server.
jtest.publishSpecifies the directory where the report will be created. By default it is ${project.build.directory}/jtest.
jtest.reportSpecifies 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.resourceA list of resource parameters. Can be configured by property since Maven 3.0.3.
jtest.resourcesAn 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.settingsA list of settings parameters. Supported by Maven since 3.0.3. Can be configured by property since Maven 3.0.3.
jtest.settingsListDisplays 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.showsettingsAllows you to skip the Jtest execution phase. If set to true, only the jtest.data.json data file is generated.
jtest.skipFull name: com.parasoft.jtest:jtest-maven-plugin:2020.1.0: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:2020.1.0: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.publishSpecifies 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.resourceA list of resource parameters. Can be configured by property since Maven 3.0.3.
jtest.resourcesAn 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.settingsA list of settings parameters. Supported by Maven since 3.0.3. Can be configured by property since Maven 3.0.3.
jtest.settingsListDisplays 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.showsettingsAllows you to skip the Jtest execution phase. If set to true, only the jtest.data.json data file is generated.
jtest.skipThis 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 |
|---|---|---|---|
| jtest.referenceStore | Path | The path to the cache directory where the reference files are stored when downloaded from URLs specified with the The cache files are used as a baseline for test impact analysis until they are removed from the specified directory. When removed, they are re-downloaded from the URLs. |
| runFailedTests | jtest.runFailedTests | 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 | jtest.runModifiedTests | true | false | Enables including new and modified tests (even if they were not affected by production code changes) in the test run. The default is: |
| settings | jtest.settings | Path | The path to the .properties file that includes custom configuration settings. |
| settingsList | jtest.settingsList | A list of The settings configured in the jtest.properties file located in the Jtest installation directory are automatically included. | |
| testFilter | jtest.testFilter | Pattern | Specifies additional tests to include or exclude. You can use glob patterns to match more filenames. In the following command-line example, Jtest will re-run all tests that match the
|