Forum Discussion

kroe761's avatar
kroe761
Contributor
10 years ago

TC 11.1 and Chrome 45 test playback very slow?

Ever since I upgraded to TC v11.1 and Chrome v45, my test performace has slowed drastically.  I have three test projects, each running as a distributed network test in seperate VM's, all running in Chrome (internal business applications, programmed by the devs to run in Chrome).  I ran one test in Chrome and it finished in 3:30 minutes, but in Firefox it ran it 1:11 minutes.  Before the upgrade, a project that ran in about 1.5 hours now takes over 3, another one that used to take about 3 hours now runs in about 4.5 hours, and another one that took 2.5 hours now runs in over 8 hours.  Fore the third one, a major chunk of the tests revolve around a Kendo UI grid.  Now, for some weird reason, TC cannot find the columns button as shown here (http://screencast.com/t/cDhXmTum1a).  This, however, does NOT work in Firefox.  This used to work in v11.0 for Chrome.  is anyone else experiencing issues like this?  Thanks for your help!

10 Replies

  • brk9394's avatar
    brk9394
    Occasional Contributor

    Hi,

    I have not yet updated to TC11.1 (still on 10.5), so this may be unrelated to your problem. However, I've had numerous issues with Chrome performance, and found that most of them were due to using the "contentText" property with the Find/FindChild methods. The issue was also compounded by the object's depth in the DOM relative to the parent object. For example, I had one Find statement that took about 4 minutes to locate the object in Chrome using contentText; after switching the property to use 'innerText' instead, it ran in about 5 seconds (similar to FF & IE). In that example, the depth was 10 levels below the parent object on a complex page. After some experimenting I found that for each level deeper (relative to the parent object), over 20 seconds to the overall search time. In most cases I was able to simply convert the 'Find' to use the 'innerText' property (or 'idStr' if available, or some other property), and the Chrome performance has been OK for me since.


    Here is another related post on the issue.

     

    Otherwise, if this is not the issue, I'd suggest to try to limit the test to a single area, then check the Test Log timings compared between Chrome and FF to help narrow it down.

     

    (btw, your screencast link has some extra characters at the end of it). For the Columns button, can you still spy the control? If not, you may need to update the TC browser patches (or disable the browser auto-updates and manually upgrade them when needed).


    Hope that helps,
    Brian

    • kroe761's avatar
      kroe761
      Contributor

      @brk9394

       

      Thanks for the info!  I'm now activly trying to avoid contentText, and I was using it everywhere.  The odd thing, though, is that until the update the performace was much better, including using contentTexts.  But still, thanks!

       

      @TanyaGorbunova

       

      I was running the tests in a windows VM used solely for these tests.  There were no extensions enabled.  

      • Hi Kroe761,

         

        I would recommend that you contact our TestComplete Customer Care Team ( http://support.smartbear.com/product-list/ ) to troubleshoot this behavior. Several users have already complained about the slow performance in Chrome 45+TestComplete 11.1 in the Community. Our R&D team is trying to find the cause of this behavior. If you provided them with the steps to reproduce the issue, that would be awesome.

         

        Thanks in advance.

         

  • Hi Kroe761,

     

    Could you please troubleshoot the issue by disabling extensions installed in Chrome (don’t disable TestComplete’s extension)? Does it affect the performance issue?

  • Im having the same issue. Just updated to 11.10.1005.7 and tests are sometime taking up to 5mins to click an object or setText in field.

    I also use contentText a lot so disabled this and all chrome extenstion bar TC's and its a little quicker but not much.

    • william_roe's avatar
      william_roe
      Super Contributor

      I'm finding 'FindChildByXPath' to be crazy slow as well.

      • TestingHobo's avatar
        TestingHobo
        Contributor

        Yep, same tests is taking nearly 4x as long...

         

        IE 11 = 129 seconds to run

        Chrome 45 = 452 seconds to run