Forum Discussion

hannecroonen's avatar
hannecroonen
Contributor
3 years ago

Object lookup is acting strange

Hi all,   I have a question regarding object lookups; I am using this in my tests since I have to check if certain windows are showing or not at the right time. To reduce my code duplication I...
Name Mapping
Test Results
Test Run
  • hannecroonen's avatar
    hannecroonen
    3 years ago

    Hi Marsha,

     

    I know how the wait functions work, I use them a lot throughout my testing framework!

    Problem is this function has maybe 200 windows that I need to check and if I would use the wait functions this would delay the program by minutes if not hours so that is not feasible...

    I do think this object lookup functionality is not what I was searching for so I went back to using switch cases instead and this works perfectly, I just tried to find a shorter way to implement this.

hannecroonen's avatar
hannecroonen
Contributor

Hi Marsha,

 

it is not that I need all of them to show up.

This is a function that only checks if at a certain step a certain window is shown.

I tried to put this all in one function instead of making numerous smaller functions that all do the same but at different steps in the process.

So for example; if the 'free costs' window should be up -> I run this function but it should only search for that window, not for all the rest in the function...

Marsha_R's avatar
Marsha_R
Moderator
3 years ago

Read here about the Wait functions. These are built in functions in TestComplete that already do what you are trying to create.

 

https://support.smartbear.com/testcomplete/docs/app-objects/common-tasks/waiting-process-or-window-activation.html

 

For your 'free costs', you would use WaitWindow  then use Exists to make sure it is there when the Wait is done.  There are a lot of examples on that page so you can see how it works.

 

try this on one of your objects and let us know what happens.

 

 

  • hannecroonen's avatar
    hannecroonen
    Contributor
    3 years ago

    Hi Marsha,

     

    I know how the wait functions work, I use them a lot throughout my testing framework!

    Problem is this function has maybe 200 windows that I need to check and if I would use the wait functions this would delay the program by minutes if not hours so that is not feasible...

    I do think this object lookup functionality is not what I was searching for so I went back to using switch cases instead and this works perfectly, I just tried to find a shorter way to implement this.

    • Marsha_R's avatar
      Marsha_R
      Moderator
      3 years ago

      It would be about 30 minutes if you use the default time out, which I agree is too long, but we worked out ours by changing the wait time between test steps just a little and then changing the default time for the Wait to be shorter. Slowing down the test steps gives more time for the windows (and anything else) to be available before TC looks for it and then the Wait rarely if ever fails.