Currently, (as per TestComplete help) TestComplete only checks for unexpected windows when the script performs an action (Click, DblClick, Activate, etc.). The check does not happen when the scri...
> Actually, it is enough to try to activate some window (e.g. formWindow.Activate() ). If the formWindow is overlapped with some modal window, the OnUnexpectedWindow event will be triggered.
I'm referring to the following limitation:
The check does not happen when the script performs certain operations with window properties or when it executes a function, for example, WaitWindow.
We are testing an application where there are lots of 'WaitWindow' actions due to the response from hardware. Now, during the 'WaitWindow' if a disconnection happens, it can sometimes throw a popup or other errors. Since the system is not stable yet, we cannot predict what will happen and which popup will be shown. This limitation with the 'WaitWindow' makes it unable to handle such cases.