| Wrong Button clicked [message #1857541] |
Tue, 14 February 2023 15:41  |
 Mike Bray
Messages: 60
Registered: May 2019 |
Member |
|
|
I have a SWING application which has a tab pane. This tab pane can have 2 or 3 tabs depending on user choice. At the bottom of the screen is a number of buttons which can be invisible or not depending on the tab being displayed.
see enclosed file objectmapping issue QL.png
I have a test case that is for a particular set up (number of tabs and buttons) where I have mapped the component name/technical name to a particular button. The correct text shows up in the Object Mapping screen.
i.e
Button Component ("Close")
closebtnsec
However when I run the test in a test suite it clicks on the button before it.
See enclosed file objectmapping issue jubula.png
Are ComponentName/Technical Name/object mapping unique to an AUT or does is combination this common to all AUTs?
If I delete all of the technical names from my AUT will it affect the other AUTs?
Mike Bray
|
|
|
| Re: Wrong Button clicked [message #1858998 is a reply to message #1857541] |
Thu, 04 May 2023 22:29  |
Milos Hroudny
Messages: 24
Registered: June 2017 |
Junior Member |
|
|
Hi Mike, I do not know whether you still have the reported problem but I try to share my experience.
Object mapping can be a little bit tricky.
By my opinion the reason could be the used heuristics.
If you prepare your test case and go to the screen of an application
you usually get proper component object mapping.
Anyway if you prepare some steps of the test case,
it can happen that the previously mapped object
is not found as required. From this reason I suggest
to let run the test case through test steps till the
moment when you need to click the mapped object.
At this point switch on object mapping functionality,
move mouse over your tab that shoul be clicked
and when the tab is green marked repeat your
mapping. There are to possible cases here.
1.There is marked your previously mapped component
in the list of mapped components by green or yellow
point. In this case your mapping should work.
If not, try execute all test cases in a suite with
the actually developed TC as the last one and repeat
attempt to map object.
2.Even though you mapped already the object
in the past, after object mapping is created a new
technical object. In this case you should use the new
mapped object to reach your object.
You can also revert the steps. With switched on
object mapping move your mouse pointer over
originally mapped object in mapper and select context
menu to show the object in the application. I expect
that there is green rectangle on other tab than you
want. If yes, make a new mapping. By my experience
the visually same screen can produce for some
objects different mapping for different previous
conditions/steps. From this reason is also good idea
to introduce some structure in your object mapping
and not keep all mapped objects in one list.
On the other hand you do not need always destroy
previously prepared mapping. Just use new unique
logical name, map it to the new found technical
name and this new mapped object move to some
proper folder in the mapped objects structure.
Hopefully my hint helps.
[Updated on: Thu, 04 May 2023 22:52] Report message to a moderator |
|
|
|
|
Powered by
FUDForum. Page generated in 0.02153 seconds
] 
Search
Help
Register
Login
Home
