...

This option specifies the location of the custom json.data.file. See Creating a Custom .json Data File.

-resource <path relative to the project>

...

• include com/** (tests all files in packages whose qualified names begin with "com)
• include **/*Account (tests files whose qualified names end with "Account")
• include path:**/Bank.java (tests only Bank.java files)
• include path:C:/Project/src/** (tests all subdirectories and files in C:/Project/src/)
• include path:C:/Project/src/examples/runtime/* (tests all files in C:/Project/src/examples/runtime, but not subdirectories)
• include c:/include.lst (tests all files listed in the include.lst file ; each line is treated as a single pattern)
• exclude **/internal/** (tests everything in the primary testing scope except files that have "internal" as part of the package name)
• exclude path:**/tests/** (tests everything in the primary testing scope except the files in the "tests" folder)

Alternatively, you can specify a list of patterns in a  .lst file and pass the file with the -include or -exclude switch. Each line in the file will be treated as a single entry.

-data.update <pattern>

This option specifies project compilation data you want to add or overwrite in a JSON data file. It allows you to manually modify your JSON file by configuring the classpath, bootpath,sourcepath, binarypath, encoding, and sourcelevel with one of the following instructions:

...

See Compilation Data Model for details.

See .Configuring+the+Test+Scope+v10.4.0 for details about configuring the test scope.

Anchor
creating_json creating_json

Creating a Custom JSON

...

Customizing Configuration

-settings <path>

This option specifies the path to a custom .properties file that includes customized settings in the following format: key=value (for example, report.format=pdf). You can use this option multiple times to specify several .properties files. Entries with the same key will be overwritten. Example:

• -settings Project1Config.properties

...

This option allows you to configures a single setting directly in the command line.  Use the following format: key=value.

You can use this optoin option multiple times to configure several settings on the came same command line. Earlier entries with the same key will be overwritten. Examples:

...

Anchor
workspace workspace

-workspace <path>

This option specifies the path to a custom location of the .jtest directory, where run-specific data is stored during analysis.

-showdetails

This option increases console verbosity to display progress details.


...