Forum Discussion
Yes I can confirm that wndWindowContent is present. This is a very top level element that is pretty much always present. For giggles I stopped the execution of a test at this point in code and confirm with the highlight element that it is present and very quickly identified.
Hi,
> Aliases.browser.pageMain.wndWindowContent.WaitAliasChild("panLogin", ProjectSuite.Variables.TinyWaitTimeout);
> wndWindowContent is present. This is a very top level element [...]
This might be the reason depending how panLogin alias is mapped.
Guessing that if it is mapped using Advanced Find, then TestComplete will drill-down complete objects tree in order to check if the sought for alias exists.
The more definite and precise identification criteria and search path are defined in NameMapping, the more fast .WaitXXX() method will work.
- vthomeschoolmom5 years agoSuper Contributor
So I am guessing by Advanced Find you mean extended search? It WAS using extended search. And it did not need to. I removed the selection of extended search on wndWindowContent. I confirm that it is still found properly. That element is used all over the place and does not take a long time to find. panLogin, when present, is found immediately. When NOT present, the timeout is not being honored. That is the crux of my issue.
Thanks
- vthomeschoolmom5 years agoSuper Contributor
I replaced the WaitAliasChild with FindChild and properties. It is much faster. Still kinda wonder why WaitAliasChild is taking so long. I want it to timeout when I want it to! I don't love the FindChild in this case since it mimimizes the effectiveness of reuse of a well constructed NameMapping. Ah well. Such is life.
- tristaanogre5 years agoEsteemed Contributor
Can you screenshot your NameMapping of the relevant section, making sure you expand to show the "Extended Find" column? Also, a bit more of your workflow/automation in a screenshot would be helpful. Obviously, there's a reason why you're waiting at that point... but I wonder if there might be something else that needs to be considered. If this is a web page, there could be other Active components and loads and things that are happening that calling WaitAliasChild at that point is causing other things to trigger.
This could also be a caching thing. Have you tried calling "RefreshNameMapping" on the parent object before you call WaitAliasChild?
Related Content
- 6 years agorizzomeister
Recent Discussions
- 2 hours agoashly