Eclipse Community Forums: Jubula » Jubula, CI and Version Control

Home » Archived » Jubula » Jubula, CI and Version Control

Jubula, CI and Version Control [message #882713]

Wed, 06 June 2012 23:01

Eclipse User

Based on what I've read in the forums and through blogs, integrating Jubula into a Jenkins based CI system should not be too difficult. In terms of version control and updating of exported testing project xml files, here are a couple of suggestions:

1. From my understanding, to update a test project in Jubula from a CI environment, you need to delete the project and then import the project xml file using the dbtool. Perhaps there could be command-line parameters such as "--overwrite" which explicitly does this as one step. Additionally, this, "--overwrite" option need only be performed if the project xml file modification is later than the last update to the project.
2. A graphical diff tool for different project xml file versions would be useful. If multiple testers/developers are working on the same test project and there are merge problems with the commited project xml file/s this could be a useful toll compared to using a plain text diff tool.

[Updated on: Wed, 06 June 2012 23:05] by Moderator

Re: Jubula, CI and Version Control [message #882774 is a reply to message #882713]

Thu, 07 June 2012 03:06

Eclipse User

1) A simple --overwrite would collide with other options (i.e. the house keeping like keep summaries). Nevertheless this is a good idea. Please file an enhancement request against Jubula in Eclipse Bugzilla.

2) The current format is not suitable for comparison. We are evaluating EMF as a replacement architecture. If this works out, model comparison is hight on our to-do list. Please expect no result before Q1 2013.

Previous Topic:	Screenshot comparison
Next Topic:	Writing extensions for custom SWT/RCP components

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 27 13:18:27 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter