Extending the RCP-Toolkit [message #1651933] |
Thu, 05 March 2015 15:55 |
Janine Kayser Messages: 14 Registered: November 2012 |
Junior Member |
|
|
Hi,
I'm currently evaluating Jubula and have a look at how much of our product we can test with it. A major part of out product consists of a nebula grid widget. Since this is not included in Jubula's default toolkits I'm currently looking into making our own toolkit plugin for this purpose.
I m currently having the problem that I can see the components and actions added by my plug-in but I'm not able to start my RCP-Application anymore via Jubula. How can I extend the RCP toolkit without loosing the functionality for starting and automatically generating names
Since I'm still kind of new to the usage of Jubula can you please tell me where my problem is?
It might be because my ToolkitProvider extends SWTToolkitProvider since ToolkitProvider from toolkit.rcp.provider is not exported by its plug-in.
Current Situation
My project/AUT configutation uses both use "Extended RCP Toolkit" as toolkit.
ExtendedRCPToolkitProvider
package org.example.jubulaplugin.nebula.grid.toolkit;
import java.net.URL;
import java.util.ResourceBundle;
import org.eclipse.jubula.toolkit.common.utils.ToolkitUtils;
import org.eclipse.jubula.toolkit.swt.provider.SWTToolkitProvider;
public class ExtendedRCPToolkitProvider extends SWTToolkitProvider
{
public static final String L18NBUNDLE = "org.example.jubulaplugin.nebula.grid.toolkit.i18n.i18n";
@Override
public URL getComponentConfigurationFileURL()
{
return ToolkitUtils.getURL(Activator.getDefault().getBundle(), "resources/xml/ComponentConfiguration.xml");
}
@Override
public ResourceBundle getResourceBundle()
{
return ResourceBundle.getBundle(L18NBUNDLE);
}
}
ComponentConfiguration.xml
<compSystem xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../org.eclipse.jubula.toolkit.common/resources/xml/ToolkitComponentConfiguration.xsd">
<configVersion>
<majorVersion>1</majorVersion>
<minorVersion>0</minorVersion>
</configVersion>
<toolkitComponent type="org.eclipse.nebula.widgets.grid.Grid" visible="true">
<testerClass>org.eclipse.jubula.ext.ExtendedRCPTester</testerClass>
<realizes>org.eclipse.swt.widgets.Tree</realizes>
<componentClass name="org.eclipse.nebula.widgets.grid.Grid" />
<action name="CompSystem.Less" changed="1.11">
<method>rcVerifyText</method>
<param name="CompSystem.Text">
<type>java.lang.String</type>
</param>
<param name="CompSystem.Operator">
<type>java.lang.String</type>
<defaultValue>equals</defaultValue>
<valueSet>
<element name="CompSystem.Equals" value="equals" />
<element name="CompSystem.NotEquals" value="not equals" />
<element name="CompSystem.MatchesRegExp" value="matches" />
<element name="CompSystem.SimpleMatch" value="simple match" />
</valueSet>
</param>
</action>
</toolkitComponent>
</compSystem>
Please don't mind the defined action. I only chose a name that i could identify quickly for testing purposes.
plugin.xml
<plugin>
<extension
point="org.eclipse.jubula.toolkit.common.toolkitsupport">
<toolkit
IToolkitProvider="org.example.jubulaplugin.nebula.grid.toolkit.ExtendedRCPToolkitProvider"
includes="com.bredexsw.guidancer.RcpToolkitPlugin"
isUserToolkit="true"
level="toolkit"
name="Extended RCP Toolkit"
order="11"
toolkitID="org.example.jubulaplugin.nebula.grid.toolkit">
</toolkit>
</extension>
</plugin>
I m not using the feature and update site mechanics. For easy testability I'm just exporting the plug-in, putting it into Jubula's plugin folder and reffering to it in the osgi.bundles of the config.ini.
[Updated on: Fri, 06 March 2015 09:54] Report message to a moderator
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04012 seconds