Forum Discussion

holliec's avatar
holliec
New Contributor
12 years ago

Test Complete 10.40 and Chrome 38 DPI Settings

I am running TC 10.40 on Windows 7 Professional 64-bit, and updated Chrome from 37 to 38 on the stable channel last week.  (After the update, I ensured the extension was still enabled, and it was.)  Immediately after updating from 37 to 38, Test Complete was unable to find any objects.  (It navigated to the correct pages just fine, but it was unable to find objects on the page to perform any actions).



A couple of days ago, I worked with Rick.  We were able to get my tests to execute successfully again by changing my system DPI settings from 125% (default) to 100%.  Please bear in mind that I have never changed the DPI settings on my machine in the two years I have owned it, nor do I ever change the zoom level for Chrome, and I run Test Complete on this machine every day.  This issue strictly arose from the 37 to 38 Chrome update.



After further reading on other forums, I can see that this is not a rare issue, and the DPI settings with Chrome are a known problem. Here are some examples:








Although this is an issue with Chrome, I believe it warrants extra investigation by the Smart Bear team since it does impact some Test Complete users, such as myself.  



By following the advice in the above forums, the DPI scaling is fixed by changing the path to include " /high-dpi-support=1 /force-device-scale-factor=1". However, after doing so, Test Complete can no longer find the path to the Chrome browser, and I have not yet found a solution to tell Test Complete to find it with this modified path. Thus, I still have to run my system DPI at 100% to get my tests to execute properly, when previously they were fine with 125% on previous versions of Chrome.



Again, I think extra investigation into this would be appreciated by your Test Complete customers. There should be an alternate solution to get Test Complete to recognize objects in Chrome 38 besides changing the DPI settings from the default 125%.

6 Replies

  • rowell_selvano's avatar
    rowell_selvano
    12 years ago
    I have the same problem with Hollie but changing the DPI settings didn't work for me. The problem is not really finding the Object. It is actually there but seems hidden. TestComplete does recognize the object but it could not find its properties. I tried using aqObject.GetProperties or aqObject.GetMethods to actually make the properties of the Object to show up but with no luck. 



    Basic sample:


      var js = Sys.Browser("*").Page("*").contentDocument.Script;

      js.eval("tcAjaxRequest={responseData:null, status:'Pending',complete:false }");



    When you debug js in IE, you can see tcAjaxRequest together with other properties of the browser page. In Chrome, you can't. 



    I agree that SmartBear has to do some research on this issue.
  • TanyaYatskovska's avatar
    TanyaYatskovska
    Icon for Alumni rankAlumni
    12 years ago
    Hello Hollie,

     


    I did found your support case with Rick. You had a call with him. So, the issue was discussed and resolved mostly during this call. If Rick informed you that the QA team would investigate this behavior, then it's fine. I played with DPI settings on my computer, and they didn't affect the recognition of web objects in Chrome. Perhaps, this behavior is computer-specific, and some other factors affect it.


     

  • dganov's avatar
    dganov
    Icon for Staff rankStaff
    12 years ago
    You wrote:

    By following the advice in the above forums, the DPI scaling is fixed by changing the path to include " /high-dpi-support=1 /force-device-scale-factor=1". However, after doing so, Test Complete can no longer find the path to the Chrome browser...



    This is a little strange. How do you run Chrome in your test and how do you set up its command line parameters? Maybe you should use double slashes?
  • TanyaYatskovska's avatar
    TanyaYatskovska
    Icon for Alumni rankAlumni
    12 years ago
    Hi Guys,

     


    Could you please contact our Customer Care team to investigate the situations? Our QA team has tested Chrome 38 with TestComplete 10.4 and didn't find any serious issues. Perhaps, your issues are computer-specific. Anyway, I'm sure they will try to help.


     

  • holliec's avatar
    holliec
    New Contributor
    12 years ago
    Hi Tanya,



    Did you even read my full post? I already worked with Rick. The issue here is that I had to change the DPI settings when they have *NEVER* been touched before. Please carefully re-read my post and the applicable links pertaining to this issue.  



    Thank you.
  • holliec's avatar
    holliec
    New Contributor
    12 years ago
    Tanya.



    This is very simple. The support call with Rick was-- let me reiterate this again-- in my ORIGINAL post above.



    Once again-- it has never been addressed as to WHY I had to change the DPI settings from 125% (DEFAULT) to 100% (NOT DEFAULT) to get the tests to execute. The ONLY variable that changed in my test environment is that I upgraded from Chrome 37 to Chrome 38 when the stable channel updated. NO other changes were made to this machine running Test Complete.



    Having to repeat the same information three times is quite tiring, for this is a very simple issue. It appears as though I will just have to trouble-shoot this on my own, and/or accept running the system at 100% DPI to get the tests to execute, since we seem to be no closer to any alternatives. This is a very poor non-solution to a very real problem.