Forum Discussion
HI handanu ,
To over come the mentioned issue , one possible way is, change the "DesktopAlert" to wildcard value , ie, WPFObject("xxxWindowxx","*"). This might solve the issue for time being, but i dont know exactly why the values change by time.
Hi,
Thank you or your reply.
But this time I get "Ambigious recognition of the tested object" warning. It takes time to find the alert.
I keep the alert window manually to see the warning.The alert window is invisible after a while (program's behaviour). So if I do not keep the alert manually, the alert will disappear and I will get an error again.
- handanu5 years agoContributor
I guess I have found a way. I have changed the location of the object in name mapping and aliases section. I transport the object from problematic parent to reliable parent. When I run the test, it passes.
But I still don't understand why alert window's identities changed project to project.
- hkim55 years agoStaff
Nice job finding a stable parent object using the extended find! Sometimes machines are quirky and this is the best solution if we can't find a unique static path all the way down to the child object!
Related Content
- 12 months ago
Recent Discussions
- 18 hours ago