What you say may be true. That the parent object does not exist. What is problematic for me is that if the parent does not exist, then clearly the child does not. What is the point of a timeout value if the seek is not going to ... well... timeout? The documented behavior is what I am seeking here. Look until time x. When time x is reached, stop.
It has to do with the logic of the process.... in order to call the WaitAliasChild method of the parent, it needs to detect that the parent is present. Since you don't have a coded "Wait" for the parent, it uses the default wait time for the overall project for the parent before it can call the WaitAliasChild. The way the logic works, when you write
TestComplete checks each part of the tree from top down... first checks MyApp, then Parent, then it can call WaitAliasChild. The assumption made is that you've already done the necessary checks for MyApp and Parent so any attempts to access them goes back to that default timeout.
Probably, the MOST correct way of doing this is..
myProcess = Sys.WaitProcess('MyApp', 10000)
if myProcess.Exists then
myParent = Aliass.MyApp.WaitAliasChild('Parent', 10000)
if myParent.Exists then
myChild = Aliases.MyApp.Parent.WaitAliasChild('Child', 10000)
BUT... that gets bulky so folks usually shortcut places where you already KNOW that an object exists.
Since in your case the parent is not guarenteed to exist at the time you're checking, that should be your first check.
Robert's explanation is correct.
The only point for this part:
> Aliases.MyApp.Parent.WaitAliasChild('Child', 10000)
> TestComplete checks each part of the tree from top down [...]
Must be read as "TestComplete checks each part of the *NameMapping* tree from top down [...]"
Remember what has been said above: Aliases tree is the custom, stable and convenient to you, logical representation of the UI. This logical representation is mapped to the real physical layout via the translation NameMapping table.
So, when you command TestComplete to wait for some alias, TestComplete finds the alias, maps it to the object from the NameMapping table, traverses to the root object in NameMapping (Sys or Mobile) and starts navigating down the tree path searching for the relevant object and waiting for it if this current object is absent at the moment. As this object is sought for internally, TestComplete has no information as for whether this object must be already present or may appear within the generic (project-wide) timeout. Thus, TestComplete waits using the default project timeout. When TestComplete reaches the final target object (the one with the specified alias name), then TestComplete uses the timeout explicitly specified in test code.
Does this make sense?