|Jubula test case/test steps data model [message #906858]
||Sun, 02 September 2012 15:55
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,
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,
|Re: Jubula test case/test steps data model [message #909241 is a reply to message #907051]
||Thu, 06 September 2012 15:48
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
"Achim Loerke" schrieb im Newsbeitrag news:firstname.lastname@example.org...
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.
Powered by FUDForum
. Page generated in 0.02266 seconds