|Scout testing with Jubula [message #1230896]
||Mon, 13 January 2014 10:40
| Wouter R
Registered: July 2012
We have developed a scout application and try to setup GUI testing with Jubula.|
We have deployed our application as as Swing, and try to ease the way we setup tests.
So we are looking in the scout application for any way to set a name for a component but as far as we can see it is not possible (yet).
We already looked at the jubula/scout presentation sheets but we can't find anything useful.
Is there anybody out there who has the right way to setup testing for scout/swing applications? Since naming the components by hand from the Jubula workspace is doable but time consuming.
Thanks in advance,
[Updated on: Mon, 13 January 2014 10:40]
Report message to a moderator
|Re: Scout testing with Jubula [message #1231796 is a reply to message #1231673]
||Wed, 15 January 2014 12:23
| Jeremie Bresson
Registered: October 2011
Alexandra Schladebeck wrote on Wed, 15 January 2014 08:21|
Great to hear that you are testing Scout applications with Jubula. I'm not aware of any way to set a name for a component (I know that setName() is the Swing way, and setData() the way for RCP, but don't know if they are available in Scout).
A Scout application is defined by a model of the application. Basically you do not program against a UI library like SWT or Swing but you define forms and fields.
For example take a Form that allows creating lego minifigs (*). It contains:
* 1 StringField to provide the Name
* 3 SmartField to select head, torso and legs
* 1 ImageField to display a Preview
* 1 StringField (Read Only) for the Summary
* 1 Push Button to export the minifig.
Here a tree representation of the form:
(In the Java code this will correspond to inner classes)
At runtime this model gets rendered, depending on the rendering engine you use (Swing, SWT, RAP) you will get the corresponding widgets. Here an example with Swing:
Our idea is to reuse the information contained in the Scout Model (Name of the field for example) and to set it "the Jubula way" in the corresponding UI widget. This mechanism should be flexible, because you do not always want to instrument your application the same way.
As I answered in the other thread, this is something we are working on. First problem (uniqueness of the ID) will be solved with Luna M5.
(*) Example taken from our presentation: Testing a Scout Application with JUnit and Jubula
Powered by FUDForum
. Page generated in 0.04636 seconds