Champion Level 3The example I have provided for WaitProperty, works fine. If it waits until the WaitTime period, it usually indicates that the TestObj is null, can not be found or it does not have that specified property.
My guess is, it that it's a code related issue.
Champion Level 2Hi,
> indicates that the TestObj is null
Yes, this is what I expected to see in the code sample that I asked dhundley for.
In a nutshell:
-- WaitXXX methods so far worked as documented and I did not hear about any problems with them in the latest releases of TestComplete;
-- All WaitXXX methods are added by TestComplete to the UI objects identified by TestComplete. Thus, in order these methods can be called, the parent object must exist. When this cannot be guaranteed, code must first check if object exist (if (<someObject>.Exists) then <someObject>.WaitXXX(...) ). Otherwise, TestComplete will wait, but not for the result of WaitXXX method, but for the object itself. Finally, an error will be posted to test log if the object does not appear within wait timeout.
