blob: 8e4b8e2f6aaf83f621cd61150d2ee8638524b649 [file] [log] [blame]
<project xmlns="" xmlns:xsi=""
<!-- Set artifact id according to a RCPTT project name -->
<!-- Set group id based on application under test name -->
<!-- RCPTT Maven Plugin provides this packaging type -->
<!-- RCPTT Maven Plugin and RCPTT Runner are hosted in this repository -->
<name>Xored Maven repository</name>
If RCPTT tests are planned to be run on an update site,
RCPTT Maven Plugin can download Eclipse SDK of required version
for current platform from repository below (to see
an up-to-date list of available versions visit this link:
<!-- The main part of RCPTT Maven plugin -->
<!-- This element describes where to get an AUT to run tests -->
<!-- There are several ways to specify AUT location,
Uncomment an element corresponding to a most suitable way
<!-- Use AUT from current build results. [classifier] will be
automatically replaced according to the current platform -->
<!-- Or specify a path to AUT folder -->
<!-- As well AUT can be downloaded from HTTP -->
<!-- AUT can be downloaded automatically from Maven repository -->
<!-- AUT Artifact classifier is based on a current platform:
Windows 32bit: win32.win32.x86
Windows 64bit: win32.win32.x86_64
Linux 32bit: linux.gtk.x86
Linux 64bit: linux.gtk.x86_64
Mac OS X 64bit: macosx.coca.x86_64
<!-- Optionally it is possible to specify extra features to
be installed into AUT, this is useful when RCPTT tests
need to be executed using a repository assembled as
part of current Maven build.
Inside an 'injection element it is possible to specify a list of
features/plugins to install, if nothing is set, all available
features will be installed. suffix is required by p2,
otherwise it searches for a plugin with given id
Currently RCPTT Runner does not install requirements automatically,
so the full list of features to install must be explicitly set
<!-- This injection will include all available features from
repository assembled during current build -->
<!-- This injection will install a single feature from indigo -->
<!-- additional AUT args (besides taken in its ini-file) can be set
Use one argument per <arg> element -->
<!-- optional VM args can be set too -->
<!-- By default AUT's workspace is recreated each time AUT hangs and is
forcefully restarted. This is done to prevent workspace corruption from
blocking AUT startup (after test failures). If this is undesirable, use
reuseExistingWorkspace option:
<!-- RCPTT Runner location can be set using the same methods
as AUT location:
<!-- but the most convenient way is to just set its version,
RCPTT maven plugin will automatically set right groupId and
artifact ID and will download RCPTT Runner from Xored Maven Repo -->
clientId is user or organization name to charge executions
clientSecret can be retrieved at
<clientSecret>secret hash string</clientSecret>
<!-- Test options for RCPTT Runner, most popular options listed here.
Full list of options is available at:
<!-- Timeout for all tests, in seconds -->
<!-- Timeout for a single test case, in seconds -->
<!-- When set to true, in case of test failure
AUT will be restarted. This significantly
slows down execution, but may be useful
for some test suites -->
<!-- By default RCPTT Runner runs tests from a project directory,
but in some cases it might be required to import additional
projects into runner's workspace -->
<!-- By default RCPTT Runner runs all tests from workspace,
but it is possible to pass test suite names, so it
will execute only test suites from given project. -->
<!-- Sometimes it might be useful to skip a test case
(for instance because of some unresolved bug). RCPTT
can skip tests based on its tags. By default RCPTT skips
tests with tag 'skipExecution' (this value has been
chosen because on one hand it is descriptive enough,
on another hand it is unlikely that this tag name
will collide with some user's tag)
<!-- By default RCPTT generates a single HTML report file with
all tests, but it is possible to generate one file per
test -->