Forum Discussion

meenakshiyadav1's avatar
meenakshiyadav1
Contributor
7 years ago

Not able to handle a dynamic object

I am working on Xamarin based iOS application. I am not able to handle a dynamic window object. I am trying to logout from application. As soon as I click on SignOut, an alert comes up for confirmati...
  • AlexKaras's avatar
    AlexKaras
    7 years ago

    Hi,

     

    a) In the Object Browser and Object Spy click the 'View more members' link that is above the Properties/Methods tabs. This will provide you with more properties with the chance that you will be able to find those that are stable and unique enough to make it possible to identify the problematic window.

     

    b) It would help to see your code that does not work.

    Below assumes that you did not modify Aliases hierarchy and it matches Namemapping one.

    .FindChild() method must work, but you must call it for the processQaA360 object and specify search properties for AlertView.

    Another option is to enable the Extended Find option for the AlertView object in the Namemapping (this column may be hidden and you should select Field Chooser context menu option to display it) and delete the Window(8) object from Namemapping so that all its child objects move up one level. See https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/extended-search.html for more details.

     

AlexKaras's avatar
AlexKaras
Champion Level 3

Hi,

 

a) In the Object Browser and Object Spy click the 'View more members' link that is above the Properties/Methods tabs. This will provide you with more properties with the chance that you will be able to find those that are stable and unique enough to make it possible to identify the problematic window.

 

b) It would help to see your code that does not work.

Below assumes that you did not modify Aliases hierarchy and it matches Namemapping one.

.FindChild() method must work, but you must call it for the processQaA360 object and specify search properties for AlertView.

Another option is to enable the Extended Find option for the AlertView object in the Namemapping (this column may be hidden and you should select Field Chooser context menu option to display it) and delete the Window(8) object from Namemapping so that all its child objects move up one level. See https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/extended-search.html for more details.

 

meenakshiyadav1's avatar
meenakshiyadav1
Contributor
6 years ago

Thanks a lot Alex. Finally Find child method worked with approach mentioned in Point b in your answer.