Forum Discussion

wmtan01's avatar
wmtan01
Contributor
4 years ago

Performance Issue with using GetPropertyValue and checkProperty with "Exists"

Hi,   I'm not sure if someone has already noticed this before but I think it might be worth sharing and asking people about their opinions on it.   So normally we use Property Checkpoints and Get...
  • AlexKaras's avatar
    AlexKaras
    4 years ago

    wmtan01 :

    Hi,

     

    Thank you for your observation and sharing the result.

    Considering your result, my opinion and explanation is like this:

    -- object.Exists considers timeout setting because TestComplete 'knows' that the code works with the onscreen object from the Object Browser tree;

    -- aqObject.GetPropertyValue(object, "Exists") does not consider timeout because .GetPropertyValue() method works with plain COM object and has no reason to wait until the object appears if it does not exist at the moment of call. Note that  aqObject.GetPropertyValue() can be used to get a value of some property for any COM object. This is a generic method and it is not bound to onscreen objects from Object Browser tree.

     

    Hope, this explains the situation and corresponds to the implementation.

     

Marsha_R's avatar
Marsha_R
Moderator

What kind of opinion are you looking for?  As you said, it's built to do it with using the object.Property options faster, and I do that wherever I can, even when it's not an if.  It's a more direct call to the object and it makes sense to me to do it wherever that's available.  I only use the aq functions if I can't do what I want directly.

wmtan01's avatar
wmtan01
Contributor
4 years ago

Honestly I was expecting aqObject.GetPropertyValue(object, "Exists") to at least behave closely with object.Exists. And I was wondering why aqObject.GetPropertyValue(object, "Exists") did not respect the Options.Run.Timeout setting?

  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    4 years ago

    wmtan01 :

    Hi,

     

    Thank you for your observation and sharing the result.

    Considering your result, my opinion and explanation is like this:

    -- object.Exists considers timeout setting because TestComplete 'knows' that the code works with the onscreen object from the Object Browser tree;

    -- aqObject.GetPropertyValue(object, "Exists") does not consider timeout because .GetPropertyValue() method works with plain COM object and has no reason to wait until the object appears if it does not exist at the moment of call. Note that  aqObject.GetPropertyValue() can be used to get a value of some property for any COM object. This is a generic method and it is not bound to onscreen objects from Object Browser tree.

     

    Hope, this explains the situation and corresponds to the implementation.

     

    • wmtan01's avatar
      wmtan01
      Contributor
      4 years ago

      It does help a bit with understanding. Thanks! 

       

      There are a lot of things that on "theory" would behave the same way but it doesn't and this one I guess is one of those.

      • AlexKaras's avatar
        AlexKaras
        Champion Level 3
        4 years ago

        aqObject can be considered as a low-level code. Like Win API.

        For example, see the description of its .EmptyObject and .EmptyVariant properties.