If you want to test a Rich Client Platform application, you must ensure that our ”RCP Remote Control” plugin (org.eclipse.jubula.rc.rcp) is added to your AUT and that it will be started when the AUT starts. If you are working in a continuous build and test process, then we highly recommend doing this as a part of the product build, or just afterwards (Section 220.127.116.11, “Setting up an RCP AUT for testing as a part of the build process”). For testing purposes, and to get started quicker, the steps can also be done manually as follows:
|Please ensure that you follow all these steps!|
Locate the installation directory, and open the development folder.
Extract the content of the rcp-support.zip folder into the plugins directory for your RCP AUT.
RCP applications generally have a configuration/config.ini file which contains the parameter osgi.bundles. This parameter needs to be modified to allow the RCP remote control plugin to load on AUT startup. You must add ,org.eclipse.jubula.rc.rcp@start (the comma is important to delimit this argument from the others) to the end of the osgi.bundles parameter. If your AUT uses the simple configurator, then you will see this in the config.ini for the osgi.bundles parameter. In this case, the osgi.bundles parameter will reference the place where the bundles.info for the simple configurator is. Locate the bundles.info file and ensure that the org.eclipse.jubula.rc.rcp plugin is set to start (i.e. it is set to true). If you are migrating from one version of the RCP remote control to a new one, then you can also check the version number of the RCP remote control plugin.
Start your AUT normally (i.e. not as an AUT). Close it, and then start it again.
In your AUT, open--> .
In the Configuration tab, you will find a list of started plugins, in the section Plug-In Registry. You should be able to see that the following plugins are started (active) and that the correct versions of them (according to your Jubula installation) are running:
If you can see these plugins, then you can continue and start your AUT via e.g. an AUT configuration (Section 18.104.22.168, “Configuring a Java AUT to be started from the ITE”) or via autrun (Section 22.214.171.124, “Starting Java AUTs with the autrun command”).
If you cannot see these plugins, then you should speak to a member of the development team to implement the suggestions described in the section below (Section 126.96.36.199, “Setting up an RCP AUT for testing as a part of the build process”).
|When you install a new version of the ITE, you must repeat these steps with the new RCP remote control plugin. You must remove the previous RCP remote control and replace it with the new one from the new ITE installation, and update your config.ini or bundles.info file. We recommend starting your AUT once with -clean to ensure that the new remote control plugin is used.|
If you do not follow these steps, the AUT Agent will not be able to communicate with your AUT!
We recommend adding the RCP accessor to your AUT automatically in one of the following ways. Which way you choose will depend on your AUT, build process and Eclipse version, and you should check with the development team which approach is best:
Adding the RCP Accessor as a plugin to your AUT as it is being built is one way to ensure that it is present and started when the AUT starts.
If adding the Accessor during the build is not an option, then you can add it after the build via the OSGI console. The availability of this option is dependent on the version of Eclipse you use, and your AUT: It must allow this type of post-hoc inclusion of plugins for this to work.
Alternatively, you can add it after the product build using the P2 director. The availability of this option is dependent on the version of Eclipse you use, and your AUT: It must allow this type of post-hoc inclusion of plugins for this to work.
The file <installation-directory>/development/rcp-accessor-site.zip is a P2 update site from where you can easily install the Accessor through the --> menu. Note that the availability of this menu depends on the setup of your RCP application.