Forum Discussion

CraigB's avatar
CraigB
Contributor
5 years ago
Solved

How to have a test wait for a window to appear?

Hi   When starting up an application I need to wait for the login window to appear.  And then, after that I need to wait for the main window.  Etc.  TestComplete offers a function that, from it's...
  • tristaanogre's avatar
    tristaanogre
    5 years ago

    Question:

    Is <Mapped window name> the window you're waiting for?  If so... that's kind of what I was saying about the implementation of WaitWindow.

    If this is the case, the better way of doing what you want is this.

    Aliases.<TestedApp>.WaitAliasChild(<Mapped window name>, 30000)

     

    If you want to still use WaitWindow, you would need to know it's direct parent.  So, the code would be

     

    Aliases.<TestedApp>.<mapped window of parent object>.WaitWindow('*', <insert titel here>, -1, 30000)

CraigB's avatar
CraigB
Contributor

There's no wait until the call to WaitWindow, so there isn't any object being waited on.

I've tried variations on 
Aliases.<TestedApp>.<Mapped window name>.WaitWindow(

"*",
"<insert title here>",
-1,
30000),

 

including not having the -1, having up to 300000 instead of 30000, putting the class name in for WndClass.  Someone did manage to get this working in v12.60 without the -1, but those calls stopped working in v14.

tristaanogre's avatar
tristaanogre
Esteemed Contributor
5 years ago

Question:

Is <Mapped window name> the window you're waiting for?  If so... that's kind of what I was saying about the implementation of WaitWindow.

If this is the case, the better way of doing what you want is this.

Aliases.<TestedApp>.WaitAliasChild(<Mapped window name>, 30000)

 

If you want to still use WaitWindow, you would need to know it's direct parent.  So, the code would be

 

Aliases.<TestedApp>.<mapped window of parent object>.WaitWindow('*', <insert titel here>, -1, 30000)

  • CraigB's avatar
    CraigB
    Contributor
    5 years ago

    Thanks.  I assumed this would work in v14 since it was apparently working in v12.6 - I inherited this code from someone who wrote it using v12.6.  I've managed to get it working by waiting on the app itself.

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      5 years ago

      As an explanation, V 14.x has had some adjustments made to the engines for object identification to, actually, improve performance.  Part of that is to do a better job of being strict on object identification hence why you're getting the 10 second wait that you were... because you were attempting to use the object to wait for the object (calling the WaitWindow method on the object for which you were waiting).