Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Jubula » Jubula test case/test steps data model
Jubula test case/test steps data model [message #906858] Sun, 02 September 2012 19:55 Go to next message
Eclipse UserFriend
Hi all,

I'm new to Jubula (not to testing, though) and I have a question regarding
the internal data model of test cases/test steps/test suits of Jubula. How
are these internally represented? In the screencasts, they look pretty much
like EMF models?!

Why do I ask?
We would like to generate test suits from external sources, which are
actually represented as an Ecore DSL. Theoretically, this should work pretty
well, but I've to little knowledge about Jubula's internals for now. I just
flicked quickly through the binaries, but I did not find any EMF model,
though.

So, is it possible to generate those test suits/test cases/test steps
instead of creating them via drag'n'drop?

Any hint is appreciated.

Thanks in advance,

Florian
Re: Jubula test case/test steps data model [message #907051 is a reply to message #906858] Mon, 03 September 2012 08:04 Go to previous messageGo to next message
Achim Loerke is currently offline Achim LoerkeFriend
Messages: 357
Registered: July 2009
Location: Braunschweig, Germany
Senior Member

Hi Florian,

Jubula uses JPA as its persistence layer, especially EclipseLink. We are looking into migrating to EMF, but it is a really long term thing.

To generate TCs etc. you have a few options (which all involves looking at the source, look at the developer info for hints how to get it).

The easiest way is to generate an XML archive. The XSD is in the org.eclipse.jubula.client.archive project in model/archiveModel.xsd. To get some of the semantic it would be helpful to look at the XmlImporter/XmlExporter classes in the same project to see how this is supposed to work.

When you look at the XmlImporter class you will see lots of calls to POMaker and NodeMaker class utilities. These are the classes to create the entities of the data model. Together with a few calls to JPA you can create and store models. Again, it is fairly obvious in the code. Please don't try to create objects without going through the xxMaker classes because that might fail with every new version of Jubula. The archive and xxMaker interfaces have been stable for the last few releases and there are no plans to change them in the near future.

- Achim
Re: Jubula test case/test steps data model [message #909241 is a reply to message #907051] Thu, 06 September 2012 19:48 Go to previous messageGo to next message
Eclipse UserFriend
Hi Achim,

thanks for your answer. Have you ever considered to use the concets provided
by UML Testing Profile? From what I've seen so far in the screencasts those
keyword libraries and scripts can be really conveniently mapped to the UML
Testing Profile.

Marc-Florian

"Achim Loerke" schrieb im Newsbeitrag news:k21obc$h3l$1@xxxxxxxxe.org...

Hi Florian,

Jubula uses JPA as its persistence layer, especially EclipseLink. We are
looking into migrating to EMF, but it is a really long term thing.

To generate TCs etc. you have a few options (which all involves looking at
the source, look at http://www.eclipse.org/jubula/developers.php for hints
how to get it).

The easiest way is to generate an XML archive. The XSD is in the
org.eclipse.jubula.client.archive project in model/archiveModel.xsd. To get
some of the semantic it would be helpful to look at the
XmlImporter/XmlExporter classes in the same project to see how this is
supposed to work.

When you look at the XmlImporter class you will see lots of calls to POMaker
and NodeMaker class utilities. These are the classes to create the entities
of the data model. Together with a few calls to JPA you can create and store
models. Again, it is fairly obvious in the code. Please don't try to create
objects without going through the xxMaker classes because that might fail
with every new version of Jubula. The archive and xxMaker interfaces have
been stable for the last few releases and there are no plans to change them
in the near future.

- Achim
Re: Jubula test case/test steps data model [message #909594 is a reply to message #909241] Fri, 07 September 2012 11:44 Go to previous messageGo to next message
Achim Loerke is currently offline Achim LoerkeFriend
Messages: 357
Registered: July 2009
Location: Braunschweig, Germany
Senior Member

I'll leave it to Raimar or Johannes (our modeling guys) to answer that.

- Achim
Re: Jubula test case/test steps data model [message #911244 is a reply to message #909594] Tue, 11 September 2012 08:28 Go to previous messageGo to next message
Raimar Bühmann is currently offline Raimar BühmannFriend
Messages: 2
Registered: May 2012
Junior Member
Hi Florian,

the concepts of UML Testing Profile are new to me. Do you have an example for a concrete UML Testing Profile? This might help for better understanding.

Then it should be easier to answer your question and how the concepts fits to the structure of the test cases in Jubula/GUIdancer.

Raimar
Re: Jubula test case/test steps data model [message #1015834 is a reply to message #907051] Sun, 03 March 2013 13:43 Go to previous messageGo to next message
Jeremie Bresson is currently offline Jeremie BressonFriend
Messages: 118
Registered: November 2010
Senior Member
Achim Loerke wrote on Mon, 03 September 2012 10:04
We are looking into migrating to EMF, but it is a really long term thing.


I have seen 2 ecore files in your git repository:
* org.eclipse.jubula/model/jubula.ecore
* org.eclipse.jubula/model_refactored/jubula.ecore

I am very interested in the second one. (I had a look at the corresponding ecorediag)

Can you tell more about this?
Have you some prototype code somewhere?
Re: Jubula test case/test steps data model [message #1015838 is a reply to message #1015834] Sun, 03 March 2013 15:10 Go to previous messageGo to next message
Achim Loerke is currently offline Achim LoerkeFriend
Messages: 357
Registered: July 2009
Location: Braunschweig, Germany
Senior Member

Hi Jeremie,

the org.eclipse.jubula project should only be on the CDO branch of the repository. It is part of a proof of concept which has been stopped due to missing time. The core team will look into a lot of options to change the persistence layer during the annually refactoring cycle. We might decide to go for CDO or a completely different route.

- Achim
Re: Jubula test case/test steps data model [message #1016114 is a reply to message #1015838] Tue, 05 March 2013 06:25 Go to previous message
Jeremie Bresson is currently offline Jeremie BressonFriend
Messages: 817
Registered: October 2011
Senior Member
Hi,

Thanks for your answer. I will look at your prototype.

I am not an expert, but from what I have seen, EMF could be a very good technology for Jubula.

Previous Topic:Should I see the dragged node during a dragNdrop?
Next Topic:Can i delete user defined project from Default database in jubula
Goto Forum:
  


Current Time: Fri Dec 19 06:43:02 GMT 2014

Powered by FUDForum. Page generated in 0.04387 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software