Skip to main content


Eclipse Community Forums

      Home
Home » Archived » Jubula » Object Mapping not propagated from reused project
Object Mapping not propagated from reused project [message #949001] Thu, 18 October 2012 11:35 Go to next message
Eclipse UserFriend
We have a team of three testers, all of whom are set up with copies of the same projects. The base project is a set of reusable test cases. It has an AUT set up and working, and object mapping has been carried out on the AUT such that the project's test cases all work.

We are importing this library project into our own workspaces, and using it as a reusable project (basically a set of library test cases) inside our own test projects.

Unfortunately, we are finding that the test cases in the library project all fail with the error "Incomplete Object Mapping for AUT "<our_AUT>".

Our "main" projects are all set to use the same AUT as the library project, and the library project is set to be reusable.

We don't want to have to re-do all of our object mappings on three machines, with all the synchronisation issue that implies.

Is there a way to propagate the object mappings from the library project up into our "main" projects?
Re: Object Mapping not propagated from reused project [message #949079 is a reply to message #949001] Thu, 18 October 2012 13:06 Go to previous messageGo to next message
Eclipse UserFriend
OM is not exported from a project. We would very much like to do it but every time we thought we had a way of doing it someone came up with a case which wouldn't work. But we are open to suggestions. Just keep in mind that the solution must work in every case, including somebody redefining an AUT or OMs, reusing names, mixing in different projects which overlapping AUTs etc.

Achim
Re: Object Mapping not propagated from reused project [message #949588 is a reply to message #949079] Fri, 19 October 2012 01:22 Go to previous messageGo to next message
Eclipse UserFriend
Another thing I thought of while reading your post was why the three testers are using copies of the project. Would it not make more sense for them to work in a multi user database on the main project? That way, you still have to perform the object mapping, yes, but only once (I'd then do it in the main project, not in the library project).

Hope that helps,
Alex
Re: Object Mapping not propagated from reused project [message #986900 is a reply to message #949588] Thu, 22 November 2012 05:19 Go to previous messageGo to next message
Eclipse UserFriend
Thanks all. Not being able to export OM is a problem, but as Alex points out, it's probably mostly because we should be using a database to centralise our tests. We are looking into this now.
Re: Object Mapping not propagated from reused project [message #1049236 is a reply to message #986900] Thu, 25 April 2013 10:49 Go to previous messageGo to next message
Eclipse UserFriend
We are running into this same issue. We are using a centralized database for our projects. All of our projects are in the same database (some are reusable), but every time we use the reusable project we have to remap our components in the active project. Is this what you would expect or should the object mapping be carried forward when all the projects reside in the same database?
Re: Object Mapping not propagated from reused project [message #1051886 is a reply to message #1049236] Mon, 29 April 2013 06:21 Go to previous messageGo to next message
Eclipse UserFriend
Hi,

Yes, this is the expected behaviour. The Object Mapping is not shared between projects.

Best regards,
Alex
Re: Object Mapping not propagated from reused project [message #1695965 is a reply to message #1051886] Wed, 20 May 2015 11:27 Go to previous messageGo to next message
Eclipse UserFriend
Alex,
This post is rather old, but is this still the case ? We are having the same issue
Re: Object Mapping not propagated from reused project [message #1696062 is a reply to message #1695965] Thu, 21 May 2015 09:20 Go to previous messageGo to next message
Eclipse UserFriend
Hi Jeff,

thanks for your comment. Can you briefly describe your current setup and workflows?

Thanks,
Alex
Re: Object Mapping not propagated from reused project [message #1696138 is a reply to message #1696062] Fri, 22 May 2015 06:23 Go to previous messageGo to next message
Eclipse UserFriend
Jubula standalone 8.0 testing a RCP based application. I created a reusable test project to create some test cases to be used as building blocks for testing the product. Two of the test cases were for logging on/off with parameters for host:port userid/password. When trying to use them in Test/Properties/Used Projects the Component Names are no longer mapped to Objects.
Re: Object Mapping not propagated from reused project [message #1696437 is a reply to message #949079] Tue, 26 May 2015 09:38 Go to previous message
Eclipse UserFriend
Hi Jeff,

as described by Achim and Alexandra this is still the expected behavior.

Achim Loerke wrote on Thu, 18 October 2012 13:06
OM is not exported from a project. We would very much like to do it but every time we thought we had a way of doing it someone came up with a case which wouldn't work. But we are open to suggestions. Just keep in mind that the solution must work in every case, including somebody redefining an AUT or OMs, reusing names, mixing in different projects which overlapping AUTs etc.

Achim
Previous Topic:Jubula Test Environment
Next Topic:Error JVM code 11
Goto Forum:
  


Current Time: Wed Jul 23 18:02:44 EDT 2025

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

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

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly