For this purpose RCPTT has a test runner – a
command-line tool for running test cases and RCPTT maven plugin which is just
another way of invoking RCPTT runner and which allows to specify all necessary
options in a pom.xml file.
To follow the steps below please install Apache Maven and Jenkins
1. Generate pom.xml file.
Right-click on RCPTT Project and select RCPTT/Generate pom.xml:
In maven plugin configuration there is a lot of comments describing all possible things can be done here but the most important thing is where to get an application under test:
There are many ways to get it like download from http, take it from a zip file form a folder relative to current, like from a build result, or to explicitly set its location to a local folder.
2. Share to a source control system.
We use Git as an example.
Share your Project into Git Repo.
3. Create new Jenkins Job.
Go to Jenkins web interface. Create a new item here (let it be a Freestyle project).
All I need to specify here that we're going to use Git:
Add a Build Step which invokes top-level Maven targets:
Select Maven Version (define it in main Jenkins configuration settings) and set Maven goal. Add path to pom.xml.
Maven 3.1+ is required.
Let's add a Post-build Actions to produce JUnit test results in a target directory:
We can save and build our job now.
Once the build is completed xml report is generated in a predefined directory:
You can also find a HTML execution report:
4. Xvnc
$ sudo apt-get install vnc4server
Then you need to install Xvnc Plugin to Jenkins.
Jenkins > PluginManager > Available > Xvnc Plugin
Let's configure Xvnc:
Jenkins > configuration
Next, edit job and turn on Xvnc.
To work correctly, the application needs a window manager, for example Metacity. This window manager strives to be quiet, small, stable.
$ sudo apt-get install metacity
Add build step Execute shell which start window manager before invokes maven.
