[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[jubula-dev] Extension Development - JSlider-Example doesn't work
|
Hi!
I have a couple of problems getting the Jubula Extensions work.
My goal is to extend the Jubula Application with my own custom GUI-Components.
They can't be captured by default.
So I started creating an Eclipse-plug-in following the Guidelines of the
official "Functional Testing Extension Manual" (June 17, 2013) in
chapter "2.2 ITE extension".
I used the "JSlider"-Example-plug-in-Project as a functional reference (it's shipped with the Jubula Installation 7.1.0).
My environment data:
Hostdetails: Windows Vista, 32 Bit
Java SDK: 1.5 for the Toolkit, 1.4 for the Remote Control
Plugin development environment: eclipse Kepler (Classic Edition), Version: 4.3.0.v20130605-2000
Jubula environment: standalone Jubula Version: 7.1.0
standalone AUT (running on localhost)
Embedded Test-DB
The problems I experienced with the example-project JSlider:
1. The Target Platform configuration (set the Features org.eclipse.rcp
and org.eclipse.jubula.feature) mentioned in the development-guidelines
(2.2.1.3) isn't compatible with the example-toolkit-plugin-project as
there are "Required Plug-ins" in the "Dependencies"-Config such as
"org.eclipse.core.runtime" which are not supplied by these two Features.
My workaround was to add the eclipse-installation-folder with its
plugins to the Target Platform. --> "org.eclipse.core.runtime" is now
available
2. I created an "Update Site" and integrated the "Toolkit"-Feature (this
encapsulates the toolkit-plug-in also as the "remote-control"-plug-in
for the JSlider Component). Then I installed the Feature in my Jubula
Environment.
The Component with its Action is available. But when I start the AUT I get an error: "5009:AUT Start Failed" described here: http://www.eclipse.org/forums/index.php/t/490155/
My workaround was to create a clean eclipse-Fragment-Project and copying the files of the imported Project into this Fragment. I also compiled the Fragment with Java-Compiler 1.4 as this version is mentioned in the Extension-Manual. Now the error doesn't appears.
3. Now there is a problem, that I can't fix with any workaround. I started the Example-JSlider-AUT in my standalone AUT (with the Remote-Control-Fragment imported into the plugin-folder of the server-folder and customizing the "config.ini" by appending the fragment-id to the "osgi.bundles"-line and first "cleaning" the AUT-Agent by appending "-clean" at the end of "autagent.ini". I've also installed the JSlider-Toolkit-Plugin over an Update-Site in my Jubula-Application -> JSlider-Component is available in Test-Browser).
After starting the "Mapping-Mode" while hovering with the cursor over the JSlider-GUI-Component of the Application an Exception (In the AUT-Agent-Console) will be thrown, every time I move my cursor over the JSlider.
The full Exception-log is stored in "MappingMode_Exception.txt".
A Screenshot of my Project-Hierarchy can be seen in "eclipseProjects.PNG".
The problems I experienced with my own toolkit-plugin-project:
I. After installing my Plug-in over my Update-Site and restart Jubula,
the "Test-Case-Browser", also as the "Test-Suite-Browser" and other
Jubula-Components didn't load properly but throw an Exeption:
"Plug-in org.eclipse.jubula.client.ui.rcp was unable to load class org.eclipse.jubula.client.ui.rcp.views.TestSuiteBrowser"
The full Exception-log is stored in "MyExtension_StartingJubulaWithInstalledToolkit_Exception.txt"
A Screenshot can be seen in "MyToolkit.PNG".
My plug-in is structured like the example-Project. I followed the guidelines one-by-one.
I have no idea why my plug-in doesn't work as well as the example-plug-in.
I would be pleased if you give me any hints, ideas or approaches. ![Smile]()
Thank you!
Attachment:
MyToolkit.PNG
Description: PNG image
Attachment:
eclipseProjects.PNG
Description: PNG image