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

Bug 364150

Summary: Unassigned component names did not update itself after components added from test case editor.
Product: [Technology] Jubula Reporter: elvin <elvin.tan.dev>
Component: CoreAssignee: Project Inbox <jubula.tools-inbox>
Status: CLOSED INVALID QA Contact: Oliver Goetz <Oliver.Goetz>
Severity: major    
Priority: P3 CC: alexandra.schladebeck, markus.tiede
Version: unspecified   
Target Milestone: Indigo SR2   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description elvin CLA 2011-11-18 09:04:04 EST
Build Identifier: 5.2.00266

Adding new component from test editor > new test steps and saving the test case.
Try looking for the newly added component in Component Browser but was not found.

Reproducible: Always

Steps to Reproduce:
1)Add new test case
2)Add test step, add a new component
3)Save test case.
4)Close test editor
5)Open Component Browser
6)Observe that newly added component is not present
Comment 1 elvin CLA 2011-11-18 09:28:47 EST
from the component browser, it is visibile as 'unused component names' but did not appear under 'unassigned component names'
Comment 2 Alexandra Schladebeck CLA 2011-11-18 10:14:27 EST
I am unable to reproduce this error. 

Could you clarify the steps you have taken? 
- Are you looking for the component name in the Component Names Browser or in the Object Mapping Editor?
- What component did you add and how?

If you are looking in the Object Mapping Editor:
- Have you added the Test Cases containing the component name to a Test Suite that uses the same AUT as the one for which you have opened the Object Mapping Editor?
- Have you pressed F5 in the Object Mapping Editor to collect any new unassigned component names?

A general list of things to do before object mapping is here:
http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node160.html

If you are able to export your project and add it as a zipped file to this ticket, or add any screenshots of your test and the Object Mapping Editor, that would help too.
Comment 3 elvin CLA 2011-11-23 03:48:13 EST
(In reply to comment #2)
> I am unable to reproduce this error. 
> 
> Could you clarify the steps you have taken? 
> - Are you looking for the component name in the Component Names Browser or in
> the Object Mapping Editor?
> - What component did you add and how?
> 
> If you are looking in the Object Mapping Editor:
> - Have you added the Test Cases containing the component name to a Test Suite
> that uses the same AUT as the one for which you have opened the Object Mapping
> Editor?
> - Have you pressed F5 in the Object Mapping Editor to collect any new
> unassigned component names?
> 
> A general list of things to do before object mapping is here:
> http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node160.html
> 
> If you are able to export your project and add it as a zipped file to this
> ticket, or add any screenshots of your test and the Object Mapping Editor, that
> would help too.

I was expecting that the component names I have added from the 'test case editor' will be present in the 'object mapping editor' under 'unassigned component names'. But it seems like this was not the case. There are presented only in the 'component name browser' under 'unused component name'.
The workaround i did was to add the component names via the object mapping editor, then merge it with the component in the 'component name browser' from the 'unused component name' before mapping it to the 'unassigned technical names' in the 'object mapping editor'.
It would actually be more user friendly if the 'unused component names' are also presented in the 'object mapping editor' instead of only in the 'component name browser'.
Comment 4 Alexandra Schladebeck CLA 2011-11-23 07:59:53 EST
The "unused component names" are, by definition, not used anywhere in the project (they are neither used in Test Cases, nor are they mapped). So normally, it wouldn't be right to show them as needing to be mapped. I don't know how component names that you have used in a Test Case are appearing as "unused" (unless they move to "used component names" after you refresh the project?). 

The only other option I can imagine is that you are not renaming the default names (the ones with nn_nn_grc etc). I'm not 100% sure on what the behaviour is for these being shown as used or unused, because they shouldn't be left as they are, but renamed with meaningful names. Even so, any names actually used in Test Cases in a Test Suite for this AUT should appear (at the latest after refreshing the Object Mapping Editor) as unassigned component names. 

If you can reproduce the behaviour that leads to a new component name not being categorized as "used" / not appearing in the Object Mapping Editor, then you can reopen the ticket. Otherwise, thanks for posting your current solution.
Comment 5 elvin CLA 2011-11-23 10:28:00 EST
(In reply to comment #4)
> The "unused component names" are, by definition, not used anywhere in the
> project (they are neither used in Test Cases, nor are they mapped). So
> normally, it wouldn't be right to show them as needing to be mapped. I don't
> know how component names that you have used in a Test Case are appearing as
> "unused" (unless they move to "used component names" after you refresh the
> project?). 
> 
> The only other option I can imagine is that you are not renaming the default
> names (the ones with nn_nn_grc etc). I'm not 100% sure on what the behaviour is
> for these being shown as used or unused, because they shouldn't be left as they
> are, but renamed with meaningful names. Even so, any names actually used in
> Test Cases in a Test Suite for this AUT should appear (at the latest after
> refreshing the Object Mapping Editor) as unassigned component names. 
> 
> If you can reproduce the behaviour that leads to a new component name not being
> categorized as "used" / not appearing in the Object Mapping Editor, then you
> can reopen the ticket. Otherwise, thanks for posting your current solution.

How can user map a 'component name' (used or unused) from the 'component name browser' to a 'unassigned technical name'?
At present drag and drop method does not work as like from 'unassigned component names' to 'unassigned technical names'.
The workaround i used was very helpful since the 'merge component names' function work. However I stumble upon another challenge. If the 'component name A' is placed under 'used component names' and 'component name B'is placed under 'unused component names', the 'merge component names' function will not be available. This observation can be verified by holding CTRL and selecting 'component name A' and 'component name B' and then right click.
Comment 6 Markus Tiede CLA 2011-11-23 12:11:08 EST
It sounds like you may have misunderstood the concept of how component names are used - perhaps reading the documentation on component names:
http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node134.html

Or on object mapping:
http://help.eclipse.org/indigo/topic/org.eclipse.jubula.client.ua.help/html/manual/node159.html

will clarify the points you are unsure about. 

For a full overview of all the steps required to write a test, perform object mapping and execute it, I'd recommend doing the "First Steps" cheat sheet which you can start from the Help menu.