| Jubula, CI and Version Control [message #882713] |
Thu, 07 June 2012 03:01  |
 Andrew H
Messages: 7
Registered: June 2012 |
Junior Member |
|
|
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: Thu, 07 June 2012 03:05] Report message to a moderator |
|
|
| Re: Jubula, CI and Version Control [message #882774 is a reply to message #882713] |
Thu, 07 June 2012 07:06  |
|
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.
|
|
|
Powered by
FUDForum. Page generated in 0.02876 seconds
] 
Search
Help
Register
Login
Home
