| |
Supported test execution service properties
The test execution service has specific properties it supports and
various combinations of assigned values to these properties specify the
nature and direction of the test execution. These properties are input
arguments to the parameterized test execution service and each property
has additional meta-properties such as to indicate if a given property
is optional or required, how it relates to other properties specified in
the service and what the default value is if a value is not explicitly
specified. There are also some general properties that all automatable
services support.
Defined properties
The service defines the properties it supports while the client
automation adapters provide native means to set these properties. Each
property described below is set in a standard way as prescribed by each
client automation adapter (the three adapters included in TPTP are the
Ant, shell and Java adapters).
-
workspace (absolute, relative or project-relative,
optional, default is default workspace, example is "d:\workspace")
-
project (relative to the workspace, optional,
default is to create a new one to host the run, examples are
"d:\workspace\project" and "project")
-
suite (absolute, relative or project-relative,
required, examples are "d:\tests\test.testsuite" and
"junitTests/test.testsuite")
-
deployment (absolute, relative or
project-relative, optional, default is the default deployment, examples
are "d:\tests\test.deploy" and "deployments/test.deploy")
-
results (absolute, relative or project-relative,
optional, default is dependent on test type but usually in the project
root, examples are "d:\tests\results\test.execution" and
"results/test.execution")
-
overwrite (true or false indicating the
overwriting of the results or creating new results based on the old
name, optional, default is false)
-
classpath (the delimited class path for the test
execution, optional if project is specified, required if project not
specified and class path is not defined in the deployment's referenced
location properties, this value is prepended to the existing class path,
example is "d:\sut\application.jar; d:\sut\libraries\jakarta-oro.jar")
-
connection (the agent controller connection
string, currently this string will have
tptp:rac:// or tptp:iac:// as well as the host
and port number identified, optional, if specified it will overwrite
any settings stored in the selected deployment location properties,
examples are "tptp:rac://localhost:5150" and
"tptp:iac://localhost"and"tptp:rac://pulsar.eclipse.org:10002/default/user=scotts&password=secret")
-
configuration (uses a pre-existing launch
configuration, optional, but if given it will specify the deployment
and everything associated with that deployment without having to
specify it further, a launch configuration can be saved to an external
location from within the launch configuration dialogs, example is
"d:\launches\test.launch")
-
service (the service identifier, optional, if
specified it will be used instead of the included test execution
service, the default is "org.eclipse.hyades.test.tools.core.execute",
example is "org.eclipse.tptp.test.services.execute")
-
vmargs (the VM arguments to use in the automated
Eclipse instance, not transferred to the SUT VM, optional default is
none beyond the default as by the Eclipse configuration)
-
synchronous (indicates if the test
execution service is executed synchronously or asynchronously,
synchronous execution will block until the service signals completion)
Example property combinations
The service defines the properties it supports while the client
automation adapters provide native means to set these properties. Each
property described below is set in a standard way as prescribed by each
client automation adapter (the three adapters included in TPTP are the
Ant, shell and Java adapters). Refer to the TestExecutionService class
Javadoc HTML documentation for additional information.
-
suite=/home/scotts/tests/A.testsuite
-
project=B, suite=B.testsuite
-
workspace=/home/scotts/workspace, suite=/home/scotts/tests/E.testsuite
-
connection=tptp:rac:/192.168.1.112, suite=c:/tests/H.testsuite
-
workspace=d:\workspace, project=C, suite=C.testsuite
-
connection=tptp:iac:/localhost, project=I, suite=I.testsuite
-
project=D, testsuite=D.testsuite, deployment=D.deploy
-
workspace=d:\workspace, project=E, suite=E.testsuite,
deployment=E.deploy, results=latestResults.execution
-
suite=./tests/E.testsuite, results=./tests/results/latestResults.execution,
classpath=./tests/bin
-
connection=tptp:rac://localhost:10002, suite=.\tests\F.testsuite,
results=.\tests\results\latestResults.execution, classpath=.\tests\bin;.\aux\bin
vmArgs=-Xj9
Related concepts
Overview of the automatable services framework
Related tasks
Using the TPTP automatable services
Launching tests from scripts and applications
|
|
