cancel
Showing results for 
Search instead for 
Did you mean: 

Object identification issue with multiple versions of Desktop application

SOLVED
lakshmba
Occasional Visitor

Object identification issue with multiple versions of Desktop application

Hi Team

When we try to capture a specific icon in our application across version.

Say version 1 -> Icon 1 is captured as "

Aliases.OsiTraffic32.wndAfx.MDIClient.wndContracts.AfxFrameOrView140.AfxFrameOrView140.AfxFrameOrView140.page32770.page32770.btnNew"

Say version 2 -> Icon 1 is captured as "

Aliases.OsiTraffic32.wndAfx.MDIClient.wndContracts.AfxFrameOrView902.AfxFrameOrView90.AfxFrameOrView90.page32770.page32770.btnNew

Due to which the same icon is not identifying in version 2 . Can we know the reason for which the frame number above is different for the same icon. How do we overcome this issue.

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
TanyaYatskovska
Community Manager

Re: Object identification issue with multiple versions of Desktop application

Hi @lakshmba,

 

I agree with Rudolf - it seems that some dynamic property (for example, Index) is used to map an object. Explore your name mapping file and remove the dynamic properties. Please refer to the following article explaining how to do this:

https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/abou...

---------
Tanya Yatskovskaya
SmartBear Community and Education Manager

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️

View solution in original post

2 REPLIES 2
RUDOLF_BOTHMA
Community Hero

Re: Object identification issue with multiple versions of Desktop application

The most likely scenario I can think of is that the two tests weren't recorded in the exact same environment or with the exact same screen layout and therefore there are two different items that look the same but have different, say, Object Identifiers.

 

You will probably find that you can see both AfxFrameOrView140 and AfxFrameOrView902 in the tree

 

and subsequently, you will also find there are two seperate items in your Aliases tree.  My thought would be to clean up the mapping and aliases before continuing with testing.  When you create tests with recorder, TC just adds mappings and aliases as it requires.  They are a good starting point to understand the layout/structure of the page, but you will want to get down and simplify the structure before you start using it in earnest.  Rather than have an Alias AfxFrameOrView140 and Alias AfxFrameOrView902, rather have a single Alias called AfxFrameOrView and in the idetification properties, change the properties (probably ObjectIdentifier) to use a wildcard e.g.AfxFrameOrView*

 

Same goes for all the child objects with the same issue.


-------------------------------------------------
Standard syntax disclaimers apply
Regards,
TanyaYatskovska
Community Manager

Re: Object identification issue with multiple versions of Desktop application

Hi @lakshmba,

 

I agree with Rudolf - it seems that some dynamic property (for example, Index) is used to map an object. Explore your name mapping file and remove the dynamic properties. Please refer to the following article explaining how to do this:

https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/abou...

---------
Tanya Yatskovskaya
SmartBear Community and Education Manager

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️

View solution in original post

New Here?
Join us and watch the welcome video:
This widget could not be displayed.
Announcements
Top Kudoed Authors