|Tests everything in packages that begin with "com".|
|Tests only Bank.java files|
|Tests all subfiles and subdirectories of |
|Tests all files in |
Tests all files listed in
|Tests everything except classes that have "internal" as part of the package name.|
Custom .json Data Files
In typical scenarions, Jtest runs on
jtest.data.json data files that are automatically generated by build system plugins. Alternatively, you can manually create a .json file and provide Jtest with the path to that file using the
-data command line option (see ).
To manually create a data file Jtest will use for analysis, run
jtestcli with the
-project options. The available options are listed in the table below.
example.data.json file is created in the root of the project configured with the
Required. Enables generation ofa file and indicates where the file will be placed after generation. All other
the .json file by specifying the root of the project.
Provide the absolute path to an existing directory. For example:
All paths included in the Jtest report generated after analysis will be relative to the root of the project configured with this option.
|Sets the project name.|
|Sets the encoding of the project.|
|Sets the source of project. Use this option multiple times to specify multiple source folders.|
|Specifies the Java compiler compliance level.|
|Specifies the classpath.|
|Used to find and add the library to the bootclasspath|
|Specifies the path to the directory with jars that should be appended to the project classpath. View the json file to verify the order of the jars and ensure it meets your project requirements.|
|Specifies the path to the XML file with JUnit test results that will be used to generate a report. Use this option multiple times to specify multiple report files.|
|Specifies the path to the compiled project classes that will be used to generate metadata information required to perform the "Calculate Application Coverage" configuration.|