Forum Discussion

DCat1223's avatar
DCat1223
Frequent Contributor
6 years ago
Solved

Decrease time for If Object - Not Exists validation

Good afternoon everyone.  I've been out of the testing environment for a few years, but am back and getting re-aquainted with TC.  I'm testing a Web application using Keyword Tests, and want to have some validation run to ensure, in certain cases, that an object does not exist.  I'm using the If Object -Object Name - Not Exists Test Action.  This is working for me, but this step takes literally 10 minutes to complete.  I've set the Auto-wait Time Out on the step but that doesn't seem to do anything.  I'm hoping some of you folks have run into this and would be open to suggestions to cut this wait time considerably.  

  • In Tools | Options | Engines | NameMapping, there is an option about "check visible items first" or something like taht.  un check that and try again.

     

    One thing that happens is that if the object is not found in the available visible objects, it then goes and searches invisible... so, two separtae searches... slows things down.

     

    Second thing to look at..... are you using Extended Find?  If so, this could be slowing down the search...  because if you are using extended find in your namemapping tree and the object is not initially found, it does need to do a further search of the entire tree.  Try remapping the "offending" object without using Extended Find and see if this solves the problem.

2 Replies

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor

    In Tools | Options | Engines | NameMapping, there is an option about "check visible items first" or something like taht.  un check that and try again.

     

    One thing that happens is that if the object is not found in the available visible objects, it then goes and searches invisible... so, two separtae searches... slows things down.

     

    Second thing to look at..... are you using Extended Find?  If so, this could be slowing down the search...  because if you are using extended find in your namemapping tree and the object is not initially found, it does need to do a further search of the entire tree.  Try remapping the "offending" object without using Extended Find and see if this solves the problem.

    • DCat1223's avatar
      DCat1223
      Frequent Contributor

      Hey tristaanogre.  Thank you so much.  These suggestions did the trick!  This is running much better now.  The step now takes less than 10 seconds.  I really appreciate you input!  

       

      Dave.