Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Jubula » Versioning Tests
Versioning Tests [message #688298] Fri, 24 June 2011 11:49 Go to next message
Diane Mising name is currently offline Diane Mising nameFriend
Messages: 22
Registered: June 2011
Junior Member
I know that Jubula is built in to Eclipse for Testers. We do a lot of coding using Eclipse and we version all of our code with a CVS Repository. Is there a way to version tests using a CVS repository? I saw that you can version projects using Test/Create new version, but we really need to version individual tests not projects as many developers/testers will be working on the tests simultaneously. Thanks.
Re: Versioning Tests [message #688313 is a reply to message #688298] Fri, 24 June 2011 12:16 Go to previous messageGo to next message
Achim Loerke is currently offline Achim LoerkeFriend
Messages: 376
Registered: July 2009
Location: Braunschweig, Germany
Senior Member

Jubula supports concurrent modifications in the database as soon as you are using a "real" database instead of the embedded H2 DB. You have to install the additional DB drivers to do this (see "Additional Software" on the download page.

If this doesn't help you might consider splitting your tests in several projects (one for each group of testers working closely together) and reuse the projects for an overall test scenario. This works well for us and some users with similar requirements. (And it's a supported and recommended best practice with Jubula).

You may also export the projects to XML files and store them in your SCM. Be aware that there is no easy merge support for this approach. We are doing this to keep test scenarios in sync with the source code for nightly regression tests.

- Achim



Achim Lörke

Re: Versioning Tests [message #689952 is a reply to message #688313] Tue, 28 June 2011 16:22 Go to previous messageGo to next message
Joern Dreyer is currently offline Joern DreyerFriend
Messages: 7
Registered: June 2011
Location: Kassel, Germany
Junior Member

Based on http: //devnotesblog.wordpress.com/2011/06/14/automating-eclipse-jubula-tests-with-jenkins/ the idea with build server integration is to:
0. export and commit specific versions of test projects into a repository
1. let the ci-server check out the version of the test project matching the current product version
2. let the ci-server use dbtool to import the test project into a database
3. let the ci-server use testexec to execute a test suite defined in the project (will start the aut given on cmdline)

Correct?

- Jörn
Re: Versioning Tests [message #689965 is a reply to message #689952] Tue, 28 June 2011 16:41 Go to previous message
Achim Loerke is currently offline Achim LoerkeFriend
Messages: 376
Registered: July 2009
Location: Braunschweig, Germany
Senior Member

That's how we do our nightly tests and it works very well. Of course one could just use a project stored in a DB but this would make it very cumbersome to keep the tests and the software in sync (assuming that the AUT is build every night from the sources in the repo).

- Achim


Achim Lörke

Previous Topic:Eclipse Jubula on different computers
Next Topic:Oracle constraint violations on saving test specification
Goto Forum:
  


Current Time: Fri Apr 26 14:41:56 GMT 2024

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

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

Back to the top