Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 364576

Summary:	Object Mapping: create new technical nodes even if it already exist
Product:	[Technology] Jubula	Reporter:	Felix Ziesel <Felix.Ziesel>
Component:	Core	Assignee:	Markus Tiede <markus.tiede>
Status:	CLOSED FIXED	QA Contact:	Oliver Goetz <Oliver.Goetz>
Severity:	normal
Priority:	P3	CC:	72botu1bif, Achim.Loerke, alexandra.schladebeck, markus.tiede
Version:	unspecified
Target Milestone:	1.2
Hardware:	PC
OS:	All
Whiteboard:

Description Felix Ziesel

2011-11-23 07:16:33 EST

You can use the DVD example to reproduce the bug.

If you open the object mapping mode and map a component again, that is already available, a new technical node will be added with the same identifing information (Hierarchy, name,...).

I think that the object mapping mode should realize that the component is already available and select it instead of creating a new node.

Comment 1 Alexandra Schladebeck

2011-11-23 07:27:53 EST

This has also been noted in the GUIdancer bugzilla:
https://bxapps.bredex.de/bugzilla/show_bug.cgi?id=135

Comment 2 hft_10

2011-12-19 04:32:48 EST

I have the same problem.

I assigned my tree on object mapping, assigment became invalid after each restart of AUT or myt tree(test) and appears a new technical node with the same information.

Since this mapping is invalid, I get the error of "Component Not Found " during test execution.
 
The detail of my problem is also in Jubula Forum under the title "assignment of the technical name is invalid "

Comment 3 Alexandra Schladebeck

2012-01-04 04:07:17 EST

Hello hft,

I think that the two problems are actually different. The problem referred to in the original post is that names that are actually still valid and recognized (and have not changed) are falsely being recognized as new names in the object mapping editor. Here is the text from the GUIdancer bug report:

"Technical names from an application are being displayed as new (or changed)
names, even if they have not been altered. 

When comparing the information in the properties view for the two components,
it does not look like they are different from each other. 

This does not affect test execution: the old components are still found (unless
they needed to be remapped anyway), but it is confusing for testers working
with the tool."

In your case, if I remember correctly, the two technical names are indeed different based on one of the steps in the hierarchy.

Comment 4 Markus Tiede

2012-02-23 10:50:22 EST

This issue should be fixed with

http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=7ca7206b75ca97486baa96ee2521d7ca3328c0ec

Comment 5 Achim Loerke

2012-03-09 08:03:29 EST

seems to be fixed

Comment 6 Oliver Goetz

2012-03-13 09:34:52 EDT

Fix verified using current GD and Samples project 5.2 mapping already known components from all AUTs. No new technical nodes were created for already mapped components.