Hi Peter,
Very glad to hear it! Sorry I didn't have time to get back to you about the individual problems. Looking forward to your contributions.
- Zeb
On 06.08.2012 14:27, Peter Hancox wrote:
Hi Zeb,
Database connectivity to PostgreSQL now working from the launched Eclipse test instance. Just need to figure out where the image is being corrupted now. Nothing else you can help me with at this point as Im reasonably comfortable with the environment now.
Hope to post some updates to bugzilla later this week J
REGARDS
Peter
Solved the issue with getting The System Bundle was updated. The framework must be restarted to finalize the configuration change on launch.
It was due to 10 of the plug-ins in the target definition having 2 different versions. After unselecting the older version in each case, Ive been able to successfully launch the test Eclipse instance and the three Jubula perspectives are available. The error messages are next to useless for me; have to fallback to guess work in most cases !!!
Current problem is that I cannot connect to a database. Suspect this is probably due to needing to include some additional plug-ins within the launch. Any pointers as to the plug-ins that might be required for database connectivity.
TIA
Peter
My Eclipse development environment is Juno; the Jubula Target Platform appears to be related to Indigo. Is this likely to be a problem?
Tried using Indigo SR2 as my development environment to launch the test build but still get The System Bundle was updated. The framework must be restarted to finalize the configuration change on launch. So Im guessing its something else causing the issue?
From: Peter Hancox [mailto:phancox@xxxxxxxxxx]
Sent: Friday, 3 August 2012 10:26
To: 'Jubula platform and tools development'
Subject: RE: [jubula-dev] Resolving Dependencies in Eclipse After Maven Build
Hi Zeb,
Errors in SwtUtils.java shouldnt pose any problem. I fixed with an explicit cast in the source code but youre probably correct in that modifying the Eclipse Java compilation preferences would also have done the job.
Im familiar with the Eclipse launch process from Swing application development but its great to get confirmation that this is also the approach to be followed here, and the pointer on plug-in enablement is precisely the tips I need to make sure Im headed in the right direction.
Current problem is this error (The System Bundle was updated. The framework must be restarted to finalize the configuration change) on launch. This doesnt appear to be related to Jubula plug-in code; rather selection of the specific target platform required for Jubula. I can launch a test plugin with the original target platform, but as soon as I change to the target platform required for Jubula, this breaks also.
This is no doubt an issue with changing target platform, not specific to Jubula, but so far I havent found how to fix the issue. Any ideas, as I presume youve come across it before?
TIA
Peter
Hi Peter,
The errors in SwtUtils.java are probably caused by a difference in Java build preferences. It should be changeable from the Preferences dialog. I'm not aware of any standard Preferences for Jubula development, but that might be a good idea going forward.
Debugging Eclipse Plug-ins has a bit of a learning curve. I can give you some tips, though. In order to debug from Eclipse, you'll need to setup a launch configuration (http://help.eclipse.org/juno/topic/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_application_launcher.htm?cp=4_3_3_0), specifically, you should enable all Jubula Plug-ins plus dependencies through use of "plug-ins selected below only" (http://help.eclipse.org/juno/topic/org.eclipse.pde.doc.user/guide/tools/launchers/plugins.htm?cp=4_3_3_0_2) instead of "all workspace and enabled external plug-ins".
This way, you can do your debugging and the vast majority of your testing from Eclipse. Once you've got your changes working there, you can do a full build and deploy, and see if it is also working in the deployed version.
I hope this helps a bit. If you've got some specific questions, let us know and we'll try to give some more detailed information.
- Zeb
On 02.08.2012 13:33, Peter Hancox wrote:
Hi Zeb,
After setting the target platform and removing the org.eclipse.jubula project and all the example extension projects I was just left with three errors in SwtUtils.java that required a cast from long to int. I now have a workspace with no errors.
What is best practice for testing this now? Do I build an update site for the feature and plug-ins and then install from there to test? This would seem to be a long process for debugging. Unfortunately this is the area I have least experience in. Can you give me a bit of a brain dump on your code/test/deploy approach? Ive worked through the Eclipse plug-in development cheat sheets etc. but theyre pretty insignificant when compared with the complexity of something like Jubula.
TIA
Peter
Hi Peter,
You're on the right path. I think the main problem at the moment is the Target Platform. Be sure that you've configured the Target Platform as described in the Jubula Contribution Guide (http://wiki.eclipse.org/Jubula/JubulaContribGuid). Target Platforms are a concept that are integral to Eclipse plug-in development, as they basically define which plug-ins (in which version) your plug-ins require. You can configure the Target Platform in Eclipse's Preferences dialog.
There are, at the moment, a few projects that are not really used when building Jubula. I think the example extensions are not built, and the org.eclipse.jubula project is another example of this. That being said, setting the Target Platform should resolve most, if not all, of these issues.
General tips and guidelines for contributing to Jubula are defined in the Contribution Guide. For specific tips, we're also available here on the mailing list. For very specific tips about a bug you might be working on, comment on the bug directly and we'll give whatever help we can.
- Zeb
On 31.07.2012 04:21, Peter Hancox wrote:
Ive just started investigating the use of Jubula for UI testing of a Java Swing application. So far it seems to be just what Im looking for but Ive come across a couple of issues. One of which is an issue with saving screenshots to PostgreSQL database. I know PostgreSQL isnt a supported database but, being keen to avoid putting yet another database such as Oracle into our environment, Id prefer to fix the PostgreSQL image storage issue as everything else so far seems to work fine with PostgreSQL.
I dont have any experience with eclipse plug-in development but Im tackling that now. So far I havent been able to locate much information on fixing / enhancing Jubula but did find a thread that basically said:
· git clone http://git.eclipse.org/gitroot/jubula/org.eclipse.jubula.core.git jubula
· cd jubula\org.eclipse.jubula.releng
· mvn clean package
After doing this, the projects imported into eclipse now contained the missing generated code and most of the error messages were resolved. However, Im still left with 36 errors though most seem to relate to examples (e.g., Bundle org.eclipse.gef.examples.logic cannot be resolved).
I also have Bundle org.eclipse.emf.cdo cannot be resolved. Given I have the real Jubula feature installed and working, why would the imported source projects have missing dependencies?
What steps other than those listed above are necessary / recommended?
Is there a guide / hints and tips etc. for fixing / enhancing Jubula?
Other than the user forum, wiki, and this mailing list, are there other places to look for Jubula specific information?
The other problem area Ive experienced is getting the object mapper, recorder, etc. to communicate with AUTs launched using the plugin eclipse launcher though thats less of an issue for me immediately.
Thanks for any assistance as Id really like to get this working. So far I havent found any tool that meets my requirements entirely. Jubula is close, the price is right, and if Im able to fix issues in the code base then Ill be quite happy to use this as the basis for our test infrastructure.
REGARDS
Peter
_______________________________________________
jubula-dev mailing list
jubula-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jubula-dev
--
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig
Tel.: +49-531-24330-0
Fax: +49-531-24330-99
http: www.bredex.de
Geschäftsführer: Hans-J. Brede, Achim Lörke, Ulrich Obst
Amtsgericht Braunschweig HRB 2450
_______________________________________________
jubula-dev mailing list
jubula-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jubula-dev
--
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig
Tel.: +49-531-24330-0
Fax: +49-531-24330-99
http: www.bredex.de
Geschäftsführer: Hans-J. Brede, Achim Lörke, Ulrich Obst
Amtsgericht Braunschweig HRB 2450
_______________________________________________
jubula-dev mailing list
jubula-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jubula-dev
--
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig
Tel.: +49-531-24330-0
Fax: +49-531-24330-99
http: www.bredex.de
Geschäftsführer: Hans-J. Brede, Achim Lörke, Ulrich Obst
Amtsgericht Braunschweig HRB 2450