Forum Discussion

Petewilson's avatar
Petewilson
Contributor
6 years ago

Menu not selected as TC reports as not visible on screen, but i'm looking right at it.

Bit of an unusual one here and i'm very confused.   The below code is run and searches for and selects the menu item detailed. The code is used several times in a loop to build a system, so it ...
iOS
Object Recognition
  • Petewilson's avatar
    Petewilson
    6 years ago

    Thank you both and apologies for the late feedback.

     

    I have a feeling that it is some sort of delay in the screen displaying what it is looking for although i am not sure why it is only affecting that particular menu item, since they all run the same code, just with a different param to tell it what text to search for. I have increased my delays in the script and it appears to now be fine for 15 out of 16 loops.

     

    Thank you both for the input as it gave me other avenues to look at.

AlexKaras's avatar
AlexKaras
Champion Level 3
6 years ago

Hi,

 

> object spy reports it as being visible on screen, but for some reason the Watch details for it show as False for Visible on screen.

 

VisibleOnScreen is a property that should be used with caution... As it is said in the documentation, VisibleOnScreen is set to True only when the object is visible on screen at the given moment of time. Which means that if the object (control) is overlapped (for example, by TestComplete's UI), its VisibleOnScreen will be set to False. (And back to True if you switch back to the tested application itself). This fact makes debugging of the code that uses VisibleOnScreen a bit problematic (unless you have more than one monitor, so that your tested application is always visible).

One more thing - VisibleOnScreen originates from desktop/web support and personally I would be not much surprised if it has some side effects/specifics on mobiles.

Another thing to consider: wasn't the tested menu scrolled in some way before test code attempted to touch its Flooring item? If it was, then using what means? If the scroll was done from test code via the direct call to some native methods, then it could be that scroll action was not noted by TestComplete and it still considers menu item as not visible on screen.

And the last one for the moment: try to examine in the Object Browser objects that are close to the problematic menu item. It is quite possible that, for example, the item with the Autumn Landscape text overlaps menu item and thus it is considered as not visible on screen. (For example, it may be not clear to TestComplete that the text has transparent background which makes menu item to be visible.)

 

  • Petewilson's avatar
    Petewilson
    Contributor
    6 years ago

    Thank you both and apologies for the late feedback.

     

    I have a feeling that it is some sort of delay in the screen displaying what it is looking for although i am not sure why it is only affecting that particular menu item, since they all run the same code, just with a different param to tell it what text to search for. I have increased my delays in the script and it appears to now be fine for 15 out of 16 loops.

     

    Thank you both for the input as it gave me other avenues to look at.

    • Linda95's avatar
      Linda95
      Occasional Visitor
      6 years ago
      @MyPrepaidBalance wrote:

      Thank you both and apologies for the late feedback.

       

      I have a feeling that it is some sort of delay in the screen displaying what it is looking for although i am not sure why it is only affecting that particular menu item, since they all run the same code, just with a different param to tell it what text to search for. I have increased my delays in the script and it appears to now be fine for 15 out of 16 loops.

       

      Thank you both for the input as it gave me other avenues to look at.

      Which means that if the object (control) is overlapped (for example, by TestComplete's UI), its VisibleOnScreen will be set to False. (And back to True if you switch back to the tested application itself). This fact makes debugging of the code that uses VisibleOnScreen a bit problematic (unless you have more than one monitor, so that your tested application is always visible).

      One more thing - VisibleOnScreen originates from desktop/web support and personally I would be not much surprised if it has some side effects/specifics on mobiles.

      Another thing to consider: wasn't the tested menu scrolled in some way before test code attempted to touch its Flooring item? If it was, then using what means? If the scroll was done from test code via the direct call to some native methods, then it could be that scroll action was not noted by TestComplete and it still considers menu item as not visible on screen.

      • Petewilson's avatar
        Petewilson
        Contributor
        6 years ago

        Hi Linda 95.

         

        The item in question is always visible on screen and doesn't need to be scrolled on the ipad in question.

        I am lucky enough to have 3 monitors on my main machine, so i use 1 specifically for running tests to avoid the possibility of an over lapping window from another application.

         

        It could just be down to the fact that as you mention it had a side affect using visible on screen against a mobile device.

         

        Could be due to a lag with the TC Mobile Screen viewer as i'm not sure if TC is using that to view items or actually running on the device itself.