| <!DOCTYPE html> |
| <head> |
| <title>RCPTT Documentation Center</title> |
| <meta charset="UTF-8"> |
| <link rel="stylesheet" href="https://www.eclipse.org/rcptt/shared/css/bootstrap.min.css"> |
| <link rel="stylesheet" href="https://www.eclipse.org/rcptt/shared/css/main.css"> |
| <link rel="stylesheet" href="https://www.eclipse.org/rcptt/shared/css/prism.css"> |
| <link rel="icon" href="https://www.eclipse.org/rcptt/shared/img/favicon.ico"> |
| <script src="https://www.eclipse.org/rcptt/shared/js/jquery.min.js"></script> |
| <script src="https://www.eclipse.org/rcptt/shared/js/bootstrap.min.js"></script> |
| <script src="https://www.eclipse.org/rcptt/shared/js/prism.js"></script> |
| <script src="https://www.eclipse.org/rcptt/shared/js/ecl.js"></script> |
| <script> |
| (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ |
| (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), |
| m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) |
| })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); |
| |
| ga('create', 'UA-39589807-5', 'eclipse.org'); |
| ga('send', 'pageview'); |
| </script> |
| </head> |
| <body> |
| <div id="before-footer"> |
| <header> |
| <nav class="navbar navbar-default navbar-static-top" role="navigation"> |
| <div class="container"> |
| |
| <div class="navbar-header"> |
| <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1"> |
| <span class="sr-only">Toggle navigation</span> |
| <span class="icon-bar"></span> |
| <span class="icon-bar"></span> |
| <span class="icon-bar"></span> |
| </button> |
| <span class="navbar-brand">RCPTT Documentation Center</span> |
| </div> |
| <div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1"> |
| <ul class="nav navbar-nav"> |
| <li class="active" > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/getstarted">User Guide</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/faq/">FAQ</a> |
| </li> |
| <li> |
| <a href="http://eclipse.org/rcptt">Back to RCPTT Main Site</a> |
| </li> |
| <li> |
| <a href="http://eclipse.org">Eclipse.org</a> |
| </li> |
| </ul> |
| </div> |
| </nav> |
| </header> |
| <section class="content"> |
| <div class="container"> |
| <div class="row"> |
| <div class="col-sm-3"> |
| <div class="rcptt-sidebar"> |
| <ul class="nav"> |
| <li ><a href="https://www.eclipse.org/rcptt/documentation/userguide/getstarted/">Get Started</a> |
| </li> |
| <li ><a href="https://www.eclipse.org/rcptt/documentation/userguide/testeditor/">Test Case Editor</a> |
| </li> |
| <li ><a href="https://www.eclipse.org/rcptt/documentation/userguide/controlpanel">Control Panel</a> |
| </li> |
| <li ><a href="https://www.eclipse.org/rcptt/documentation/userguide/assertions/">Assertions</a> |
| </li> |
| <li ><a href="https://www.eclipse.org/rcptt/documentation/userguide/ecl/">Eclipse Command Language</a> |
| <ul class="nav"> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/ecl/new-command-guide/">New ECL Command Guide</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/ecl/excel-import-export/">ECL commands for Excel import and export</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/ecl/xml-import-export/">ECL commands for XML import and export</a> |
| </li> |
| </ul> |
| </li> |
| <li ><a href="https://www.eclipse.org/rcptt/documentation/userguide/contexts/">Contexts</a> |
| <ul class="nav"> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/contexts/workspace/">Workspace</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/contexts/workbench/">Workbench</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/contexts/launch/">Launch</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/contexts/preferences/">Preferences</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/contexts/parameters/">Parameters</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/contexts/group/">Group</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/contexts/folder/">Folder</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/contexts/default/">Default</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/contexts/super/">Super</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/contexts/ecl/">ECL Script</a> |
| </li> |
| </ul> |
| </li> |
| <li ><a href="https://www.eclipse.org/rcptt/documentation/userguide/verifications/">Verifications</a> |
| <ul class="nav"> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/verifications/text/">Text</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/verifications/treetable/">Table/Tree</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/verifications/errorlog/">Error Log</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/verifications/time/">Time</a> |
| </li> |
| </ul> |
| </li> |
| <li ><a href="https://www.eclipse.org/rcptt/documentation/userguide/procedures/">Procedures and Variables</a> |
| </li> |
| <li ><a href="https://www.eclipse.org/rcptt/documentation/userguide/runner/">Test Runner</a> |
| <ul class="nav"> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/runner/arguments/">Arguments</a> |
| </li> |
| </ul> |
| </li> |
| <li class="active" ><a href="https://www.eclipse.org/rcptt/documentation/userguide/maven/">Maven plugin</a> |
| </li> |
| <li ><a href="https://www.eclipse.org/rcptt/documentation/userguide/rap/">RAP</a> |
| <ul class="nav"> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/rap/install/">Install instructions</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/rap/recordReplay/">Record and Replay</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/rap/capability/">Capability Contexts</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/rap/rap-commands/">ECL commands</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/rap/rap-maven/">Maven plugin</a> |
| </li> |
| </ul> |
| </li> |
| <li ><a href="https://www.eclipse.org/rcptt/documentation/userguide/integration/">Integration</a> |
| <ul class="nav"> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/integration/test-rail-integration/">TestRail</a> |
| </li> |
| <li > |
| <a href="https://www.eclipse.org/rcptt/documentation/userguide/integration/zephyr-integration/">Zephyr</a> |
| </li> |
| </ul> |
| </li> |
| </ul> |
| </div> |
| </div> |
| <div class="col-sm-9"> |
| <h1>Maven plugin</h1> |
| <p>RCPTT Maven plugin (requires Maven 3.1+) is a convenient way of automating RCPTT test execution during Maven build. It automatically downloads RCPTT Runner and launches it with command line arguments.</p> |
| |
| <h2 id="quick-start">Quick start</h2> |
| |
| <ul> |
| <li>Download basic <a href="https://www.eclipse.org/rcptt/documentation/userguide/maven/pom.xml">pom.xml</a>, place it in a root of RCPTT project and modify path to application under test.</li> |
| <li>Execute mvn clean package from project's dir</li> |
| </ul> |
| |
| <h2 id="configuration">Configuration</h2> |
| |
| <h3 id="basic-plugin-configuration">Basic plugin configuration</h3> |
| |
| <p>Below is a basic POM template which can be used as starting point of automating RCPTT tests with RCPTT Maven plugin. Put it into your RCPTT project and configure as described below</p> |
| |
| <pre> |
| <code><project> |
| <modelVersion>4.0.0</modelVersion> |
| <groupId>com.company.product</groupId> |
| <artifactId>productTests</artifactId> |
| <version>1.0.0-SNAPSHOT</version> |
| <packaging>rcpttTest</packaging> |
| |
| <pluginRepositories> |
| <pluginRepository> |
| <id>rcptt-releases</id> |
| <name>RCPTT Maven repository</name> |
| <url>https://repo.eclipse.org/content/repositories/rcptt-releases/</url> |
| </pluginRepository> |
| <pluginRepository> |
| <id>rcptt-snapshots</id> |
| <name>RCPTT Maven Snapshots repository</name> |
| <snapshots> |
| <updatePolicy>always</updatePolicy> |
| </snapshots> |
| <url>https://repo.eclipse.org/content/repositories/rcptt-snapshots/</url> |
| </pluginRepository> |
| </pluginRepositories> |
| <properties> |
| <rcptt-maven-version>2.0.0-SNAPSHOT</rcptt-maven-version> |
| </properties> |
| |
| <build> |
| <plugins> |
| <plugin> |
| <groupId>org.eclipse.rcptt</groupId> |
| <artifactId>rcptt-maven-plugin</artifactId> |
| <version>${rcptt-maven-version}</version> |
| <extensions>true</extensions> |
| <configuration> |
| <runner> |
| <version>2.0.0-SNAPSHOT</version> |
| </runner> |
| <!-- The main configuration section goes here --> |
| </configuration> |
| </plugin> |
| </plugins> |
| </build> |
| </project></code></pre> |
| |
| <div>Important things to note here:</div> |
| |
| <ul class="maven maven-margin"> |
| <li>Packaging type is set to rcpttTest</li> |
| <li>Xored Maven repository added to pluginsRepositories</li> |
| <li>extensions set to true</li> |
| </ul> |
| |
| <h4 id="rcptt-runner-version">RCPTT Runner Version</h4> |
| |
| <p>Use <code>runner/version</code> to specify version of RCPTT Runner to use.</p> |
| |
| <pre> |
| <code><runner> |
| <!-- version of RCPTT Runner --> |
| <version>2.0.0-SNAPSHOT</version> |
| </runner> |
| </code></pre> |
| |
| <h3 id="rcptt-runner-vm-arguments">RCPTT Runner VM Arguments</h3> |
| |
| <p>Use <code>runner/vmArgs</code> to specify extra arguments for RCPTT Runner. For instance, to configure memory usage, the following lines can be added:</p> |
| |
| <pre> |
| <code><runner> |
| ... |
| <vmArgs> |
| <vmArg>-Xmx1024m</vmArg> |
| <vmArg>-XX:MaxPermSize=256m</vmArg> |
| </vmArgs> |
| </runner> |
| </code></pre> |
| |
| <h3 id="aut-specification">AUT specification</h3> |
| |
| <p>RCPTT Maven Plugin supports two sources of applications-under-tests — it can either use Maven artifact resolution to download AUT from Maven repository, or get it explicitly from file system or http server. The configuration of AUT is specified in plugin configuration section under <code>aut</code> element.</p> |
| |
| <h4 id="explicit-aut-location">Explicit AUT location</h4> |
| |
| <p>Path on a local file system or AUT http(s) download URL can be specified in <code>explicit</code> element. If path is not absolute, then it is assumed that it is relative to project base dir:</p> |
| |
| <pre> |
| <code><aut> |
| <explicit>../MyAut.zip</explicit> |
| <!-- equivalent to: --> |
| <!-- <explicit>${project.basedir}/../MyAut.zip</explicit> --> |
| </aut> |
| </code></pre> |
| |
| <p>Explicit AUT specification supports some initial substitution — if path contains <code>[platform]</code>, it will be replaced with the eclipse classifier of current platform (i.e. <code>linux.gtk.x86_64</code>):</p> |
| |
| <pre> |
| <code><aut> |
| <explicit>../../product/target/products/MyAut-[platform].zip</explicit> |
| <!-- when executed on win32 will be resolved to: |
| ../../product/target/products/MyAut-win32.win32.x86.zip --> |
| </aut> |
| </code></pre> |
| |
| <h4 id="maven-artifact-resolution">Maven artifact resolution</h4> |
| |
| <p>In case of Maven artifact resolution, artifact classifier is automatically set to current platform classifier, consisting of OS, Window System and architecture, for example <code>win32.win32.x86</code>, or <code>macosx.cocoa.x86_64</code>.</p> |
| |
| <pre> |
| <code><aut> |
| <groupId>com.company.product</groupId> |
| <artifactId>com.company.product.rcp</artifactId> |
| </aut> |
| </code></pre> |
| |
| <p>In this case rcptt-maven-plugin plugin determines the classifier of the current platform, assumes that packaging type is zip, and resolves the artifact using Aether, by taking the latest version. However, version, classifier and extension can be explicitly specified:</p> |
| |
| <pre> |
| <code><aut> |
| <extension>tar.bz2</extension> |
| <classifier>production</classifier> |
| |
| <groupId>com.xored.f4</groupId> |
| <artifactId>com.xored.f4.product</artifactId> |
| <version>1.0.0-SNAPSHOT</version> |
| </aut> |
| </code></pre> |
| |
| <h3 id="injections">Injections</h3> |
| |
| <p>Sometimes it might be useful to make some certain features available in testing assembly, but not included into the final product. For this purpose, it is possible to specify injection parameters for AUT to specify which features from which update sites should be installed into AUT before testing. Here's the example configuration</p> |
| |
| <pre> |
| <code><aut> |
| <groupId>eclipse</groupId> |
| <artifactId>sdk</artifactId> |
| <version>3.7.0</version> |
| |
| <injections> |
| <injection> |
| <site></site> |
| <!-- features are optional - when omitted, all features from given site will be installed --> |
| <features> |
| <feature>com.comanyname.featureid</feature> |
| </features> |
| </injection> |
| </injections> |
| </aut> |
| </code></pre> |
| |
| <h3 id="application-args">Application args</h3> |
| |
| <p>Extra command-line arguments for application and/or for Java VM can be specified like this:</p> |
| |
| <pre> |
| <code><aut> |
| ... |
| <args> |
| <arg>-clean</arg> |
| <arg>-port</arg> |
| <arg>8080</arg> |
| </args> |
| |
| <vmArgs> |
| <vmArg>-Xmx1536m</vmArg> |
| <vmArg>-XX:MaxPermSize=256m</vmArg> |
| </vmArgs> |
| </aut> |
| </code></pre> |
| |
| <h3 id="persistent-workspace">Persistent workspace</h3> |
| |
| <p>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 <code>reuseExistingWorkspace</code> option:</p> |
| |
| <pre> |
| <code><aut> |
| ... |
| <reuseExistingWorkspace>true</reuseExistingWorkspace> |
| </aut> |
| </code></pre> |
| |
| <h3 id="extra-projects">Extra projects</h3> |
| |
| <p>In case of using linked projects or folders in Workspace context, it might be required to specify an extra projects to be imported into RCPTT Runner workspace. This can be done by using <code>projects</code> element:</p> |
| |
| <pre> |
| <code><projects> |
| <project>${project.basedir}/../otherProject</project> |
| </projects> |
| </code></pre> |
| |
| <h3 id="test-options">Test options</h3> |
| |
| <p>Options related to test execution are specified under <code>testOptions</code> element in plugin configuration. There are no required options here, so by default this element is just omitted.</p> |
| |
| <p>The example below sets timeout options for the whole test suite and for a single test:</p> |
| |
| <pre> |
| <code><testOptions> |
| <execTimeout>30min</execTimeout> |
| <testExecTimeout>5min</testExecTimeout> |
| </testOptions> |
| </code></pre> |
| |
| <p>The complete list of parameters with their defaults is provided on <a href="https://ci.xored.com/doc/runner">RCPTT Runner</a> page.</p> |
| |
| <h3 id="tags-to-skip">Tags to skip</h3> |
| |
| <p>Sometimes it might be valuable to skip certain test cases during test execution, for example if tests depend on specific operating system or other environment. For this purpose it is possible to mark such tests in RCPTT IDE with some specific tag and then specify option, for example:</p> |
| |
| <pre> |
| <code><skipTags> |
| <skipTag>requiresVPNConnection</skipTag> |
| <skipTag>windowsOnlyTest</skipTag> |
| </skipTags> |
| </code></pre> |
| |
| <h4 id="test-suites">Test suites</h4> |
| |
| <p>By default RCPTT Maven plugin launches all tests in given projects (and extra projects) besides tests having tags from tags to skip list. In order to run only test cases belonging to test suite(s), the following lines can be added (suite name must match to a name of existing test suite inside a project):</p> |
| |
| <pre> |
| <code><suites> |
| <suite>MyTestSuite</suite> |
| </suites> |
| </code></pre> |
| |
| <h2 id="examples">Examples</h2> |
| |
| <h3 id="simple-project">Simple project</h3> |
| |
| <p>This is a trivial example which uses most of defaults provided by rcptt-maven-plugin.</p> |
| |
| <pre> |
| <code><project> |
| <modelversion>4.0.0</modelversion> |
| <groupid>com.xored.f4</groupid> |
| <artifactid>rcpttTests</artifactid> |
| <version>0.0.1-SNAPSHOT</version> |
| <packaging>rcpttTest</packaging> |
| |
| <build> |
| <plugins> |
| <plugin> |
| <groupid>org.eclipse.rcptt</groupid> |
| <artifactid>rcptt-maven-plugin</artifactid> |
| <version>2.0.0-SNAPSHOT</version> |
| <extensions>true</extensions> |
| <configuration> |
| <aut> |
| <groupid>com.xored.f4</groupid> |
| <artifactid>com.xored.f4.product</artifactid> |
| </aut> |
| </configuration> |
| </plugin> |
| </plugins> |
| </build> |
| |
| <pluginrepositories> |
| <pluginrepository> |
| <id>rcptt-snapshots</id> |
| <name>RCPTT Maven Snapshots repository</name> |
| <snapshots> |
| <updatePolicy>always</updatePolicy> |
| </snapshots> |
| <url>https://repo.eclipse.org/content/repositories/rcptt-snapshots/</url> |
| </pluginrepository> |
| <pluginrepository> |
| <id>rcptt-releases</id> |
| <name>RCPTT Maven repository</name> |
| <url>https://repo.eclipse.org/content/repositories/rcptt-releases/</url> |
| </pluginrepository> |
| </pluginrepositories> |
| </project></code></pre> |
| |
| <h4 id="dependent-projects">Dependent projects</h4> |
| |
| <p>Dependencies between test projects are described in the same way as it is for other maven projects, one thing to note is that type element must be set to rcpttTest:</p> |
| |
| <pre> |
| <code>... |
| <dependencies> |
| <dependency> |
| <groupid>com.xored.f4</groupid> |
| <artifactid>rcpttTests2</artifactid> |
| <version>0.0.1-SNAPSHOT</version> |
| <type>rcpttTest</type> |
| </dependency> |
| </dependencies> |
| ...</code></pre> |
| |
| <p>Current implementation assumes that all dependencies are packed and located either in local or in some of configured remote repositories which means that when using dependencies between projects it is necessary to use at least install phase.</p> |
| |
| <h2>Maven-related details</h2> |
| |
| <h4 id="phases-and-goals">Phases and Goals</h4> |
| |
| <p>For ease of use and ability of further customization, RCPTT tests projects use custom packaging type <code>rcpttTest</code>, since it is a natural way to associate a particular lifecycle with a project. The table below describes all phases used by RCPTT Maven plugin and actions performed on these phases.</p> |
| |
| <div class="beforeTable"> |
| </div> |
| |
| <table class="info"> |
| <thead> |
| <tr> |
| <th>Phase</th> |
| <th>Goal</th> |
| <th>Description</th> |
| </tr> |
| </thead> |
| <tbody> |
| <tr> |
| <td>generate-resources</td> |
| <td>org.eclipse.rcptt:rcptt-maven-plugin:resources</td> |
| <td> |
| <ul> |
| <li>Copies project to <code>target/projects/artifactId</code></li> |
| <li>Resolves all dependencies of type rcpttTest and unpacks them to <code>target/projects</code></li> |
| <li>If AUT is an archive, unpacks AUT to <code>target/aut</code></li> |
| <li>Downloads if necessary and unpacks RCPTT runner to <code>target/runner</code></li> |
| <li>Creates <code>target/results</code> directory</li> |
| </ul> |
| </td> |
| </tr> |
| <tr> |
| <td>compile</td> |
| <td>org.eclipse.rcptt:rcptt-maven-plugin:execute</td> |
| <td> |
| Launches RCPTT runner |
| |
| <ul> |
| <li>RCPTT runner workspace is set to <code>target/runner-workspace</code></li> |
| <li>AUT workspace prefix is <code>target/autWorkspace</code>.</li> |
| <li>Puts generated JUnit XML report to <code>target/surefire-reports</code></li> |
| </ul> |
| </td> |
| </tr> |
| <tr> |
| <td>package</td> |
| <td>org.eclipse.rcptt:rcptt-maven-plugin:package</td> |
| <td>Packages RCPTT project and execution results as artifacts (see below)</td> |
| </tr> |
| <tr> |
| <td>install</td> |
| <td>maven-install-plugin:install</td> |
| <td>default</td> |
| </tr> |
| <tr> |
| <td>deploy</td> |
| <td>maven-deploy-plugin:deploy</td> |
| <td>default</td> |
| </tr> |
| </tbody> |
| </table> |
| |
| <h4 id="produced-artifacts">Produced artifacts</h4> |
| |
| <div>The package phase produces two artifacts:</div> |
| |
| <ul class="maven maven-margin"> |
| <li>The project itself as primary artifact (so it can be references by other projects)</li> |
| <li>RCPTT execution results/logs/outputs and other information which can be helpful to identify the reason of failures. This artifact has classifier <code>results</code>.</li> |
| </ul> |
| |
| <div>Below is the complete list of items included into results artifact:</div> |
| |
| <ul class="maven maven-margin"> |
| <li><strong>rcpttTests.html</strong>: HTML report</li> |
| <li><strong>out.txt</strong>: Runner process output stream contents</li> |
| <li><strong>err.txt</strong>: Runner process error stream contents</li> |
| <li><strong>log.txt, log1.txt</strong>: Runner workspace logs (.log and .bak_N.log files from .metadata)</li> |
| <li><strong>log<N>[restart<M>].txt</strong>: AUT workspace logs.</li> |
| </ul> |
| </div> |
| </div> |
| </div> |
| |
| </section> |
| <script src="https://www.eclipse.org/rcptt/shared/js/main.js"></script> |
| </body> |
