Testing CASA with Gradle
ONLY EDIT THIS WITH "EDIT WIKI TEXT"
Within Gradle, tasks are used to perform actions. These tasks are implemented in Java or Groovy, and each task can depend upon other tasks. The table below describes the tasks currently available. There are two ways to supply input to tasks either on the command line or through a properties file. On the command line, properties are set like:
parameter is set to
(the path to an unpacked CASA distribution). Property files and a complete list of supported properties is discussed below. For more information about Gradle tasks in general, please refer to the Gradle user guide
|| Properties Used
|| Command Line Parameters
|log=test.dir.log|| run one or more tests (from nightly regression set of tests)
|| create stable from most recent test version
In this table
is either a single test, e.g.
, or a list of tests to run, e.g.
. The elements of the list are separated by commas and optional whitespace. The strings used to represent the test are a substring of the test name, e.g. when
is specified all tests which match
Gradle task names are "camel cased," and they can be run using just the first letter plus each "hump" letter. So
can be invoked on the command line as
instead of supplying the full name,
Property files are located in the parent of the directory containing the
build script. Only a single property file will be loaded for a given build or test run with Gradle. A number of possible property file names are checked and the first one found is the one that is selected and loaded. These names are shown in the following table in priority order:
|| File Name
is the username of the current user,
is the hostname of the current machine,
is one of