Forum Discussion

MegO's avatar
MegO
Contributor
7 years ago

Has anyone had any joy creating and running tests on different size monitors

Hi all,   My colleague and I are responsible for creating and running tests in TestComplete for our Desktop application.   The problem we face is that we both have different size monitors/Laptops...
Creating tests
DPI
Monitors
Resolution
  • tristaanogre's avatar
    tristaanogre
    7 years ago

    I can't find the specific article at this moment... but I know that it's documented in the TestComplete documentation that, in order for tests to run consistently, the scaling needs to be the same on all environments.  So, you CAN run on different resolutions just fine... we do it all the time.  However, you need to make sure that the scaling is the same on all environments.  The resolution size (1024x768 versus whatever) is immaterial.... it's the scaling that is causing your issue.  Correct that, as documented, and you should be fine.

baxatob's avatar
baxatob
Community Hero
7 years ago

Hi,

 

First of all - why your tests depend on screen resolution? Are you using image based tests or clicking by coordinates or may be something else?

 

The best practice requires that tests were independent from infrastructure changes.

  • MegO's avatar
    MegO
    Contributor
    7 years ago

    Hi baxatob,

     

    We use the click and record functionality of TestComplete for the majority of our tests. We replace click co-ordinates with -1, -1 as advised to click on the centre of an object rather than rely on the co-ordinates. Our Name mapping is dynamic (Using wild cards, AutomationIds etc)so that objects can be identified no matter where they are on the screen.

     

    The errors we usually see are "There was an attempt to click out of the windows bounds". The Tests run correctly when run on a laptop but fail when ran on a larger monitor. 

     

    It looks like the pixel difference is the cause of the issues...

    • shankar_r's avatar
      shankar_r
      Community Hero
      7 years ago

      The errors we usually see are "There was an attempt to click out of the windows bounds". The Tests run correctly when run on a laptop but fail when ran on a larger monitor. 

       

       

      This was the error we also used to get. Mostly it is related the scroll or object displayed partially on the screen when you run in small screen. 

       

      baxatob correctly pointed, Automation scripts should always  in-dependent from infrastructure. 

      • MegO's avatar
        MegO
        Contributor
        7 years ago

        Hi shankar_r

         

        The difference is we get this error on the large monitor not the smaller screen where the tests were initially created.

         

        Also I was lead to believe that by removing the click co-ordinates etc this is how you make the tests independent of infrastructure, or is there a better way?