|
|
Re: Extend jubula with a self-written RCP Plugin [message #928407 is a reply to message #928124] |
Sun, 30 September 2012 15:44 |
Marco Franke Messages: 10 Registered: April 2012 Location: Bremen |
Junior Member |
|
|
Hi,
you are right I have not a loft of experience in plugin developement. For that reason, I used a tutorial (eclispe.org/index.php/blog_article_en/items/using-data-cohesion-for-better-test-cases.html)(this is the wrong link. You have to replace eclispe.org through bredex.de), but the tutorial doesn't explain in detail to create a *.jar.
First, I used the orginial plugin of the tutorial(just downloaded it) and it doesn't work. The tutorial said, the plugin, as *.jar, has to be copied into the plugin folder of jubula. In consequence, I took the jar, copied it, restartet Jubula, but Jubula dindn't care.
Second, I used my own developed plugin and follow the same steps of deploying but it doesn't work.
The question is now, which requirements has to be satisfied that jubula use the plugin. Second, why jubula gives no exception if the plugin is not valid. In Eclipse, the syntax and so on are correct.
Thanks for your hint that I should read tutorials.
Has somenody else tried the above mentioned tutorial to extend jubula which an own function?
|
|
|
Re: Extend jubula with a self-written RCP Plugin [message #930507 is a reply to message #927998] |
Tue, 02 October 2012 11:35 |
Alejo Abdala Messages: 22 Registered: September 2012 Location: Argentina |
Junior Member |
|
|
Hi, I did manage to use my own plugins (both accessibility and functions) for Jubula. I recommend that you read "EXTEND.pdf" that ships with Jubula Standalone.
Edit: just checking, both the EXTEND and UserManual have information on developing accessibility plugins, not much on functions though. But it is quite easy, just set the target platform to your jubula installation plugins folder, build a plugin project and a feature project that includes that plugin. Deploy the feature project as "Deployable features". This will create a folder with an update site. From Jubula, go to "Install new software", point to that update site and install its contents. (Uncheck the "Group items by category" checkbox).
Just one thing I've come across (that I don't know certainly if it was the cause of the function not showing): create one extension for each function you declare. Declaring several functions in the same extension didn't work for me. (At the same time, the classes that implemented IFunctionEvaluators were inner classes, so, either that or the multiple-functions-per-extension issue was blocking me). But keeping things simple works
For functions, what I'm doing is exporting the feature project as an update site and installing it into Jubula as you would with any plugin (Help->Install New Software).
Related with this issue: does Jubula take the evaluator attribute of the extension into account? I wrote a plugin that checks something with the running jobs of the RCP but it just isn't working, because even though I defined that the 'evaluator' is the AUT, the jobs that it is seeing are the ones running in Jubula. Any hints on this side?
Thanks!
[Updated on: Tue, 02 October 2012 12:08] Report message to a moderator
|
|
|
Re: Extend jubula with a self-written RCP Plugin [message #930528 is a reply to message #930507] |
Tue, 02 October 2012 11:56 |
|
Quote:
Related with this issue: does Jubula take the evaluator attribute of the extension into account? I wrote a plugin that checks something with the running jobs of the RCP but it just isn't working, because even though I defined that the 'evaluator' is the AUT, the jobs that it is seeing are the ones running in Jubula. Any hints on this side?
The parameter is there for future use. Sorry for the confusion. This should have been documented but obviously was forgotten. For now the function is always executed in the client context. Feel free to file a bug against Jubula Documentation and an enhancement request against Jubula Core.
Thanks for your input
Achim
|
|
|
|
Re: Extend jubula with a self-written RCP Plugin [message #930711 is a reply to message #930546] |
Tue, 02 October 2012 15:09 |
|
There is no support in Jubula to get the workspace location from an AUT. That would be a scenario for a function running in the AUT. You can set a variable (using Application.storeValue) with the location and use it in your tests. This would require some maintenance when you change the location, but only in one place.
Achim
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04315 seconds