Forum Discussion

ehaartmans's avatar
ehaartmans
Occasional Contributor
13 years ago

TestComplete after update to 9.2 very slow

We just updated to TestComplete version 9.20 from 9.10.

This version is slow compared to 9.10.

Typing a line into a script is not do-able. Each letter takes about 5 seconds.



Are there similar experiences?

8 Replies

  • Yes. The problem occurred over a four-day period after upgrading to 9.2 and the editor was almost always unbearably slow. A look at the background processes showed that it was related to the CVS process activating. Some days were worse than others and it didn't appear to affect any other apps. We're using v 9.20.2460.7. The problem has not recurred.
  • ehaartmans's avatar
    ehaartmans
    Occasional Contributor
    We are using ClearCase for source control.

    Just tested it by making a new projectsuite which is not under source control.

    Then there seems to be no problem ...
  • cmatusz's avatar
    cmatusz
    New Contributor
    We've noticed the issue too with TC 9.20 and MS TFS for our source control.  Editing a script is not unbearable but the issue is most noticeable when using the backspace key to delete characters.  If you hold the backspace key down then let up it'll take off erasing more characters than you intended, since the key strokes are queued up and delayed.

  • Hi Guys,


     


    There is a known issue with TestComplete 9.20 - slow scripts and keyword tests editing in projects added to SCC. Please contact our Support team to get a patch that fixes this issue!


     

  • After applying the patch below, upgrading to an enterprise client and setting up several Windows 7 virtual machines a new problem was encountered. We're using PushOk v1.5.06 and CVSNT. Prior to the upgrade all script files were checked into CVS by default using a binary filetype. To be honest, since it was working, I didn't pay any attention. Post, upgrade, script files were checked in by default as text. Problems were only found on post upgrade scripts, which appear to occaisionally save as unicode. The temporary fix is to checkout  the files via Eclipse, paste the ASCII text and commit.  Now about 80% of my scripts are stored as binary and the rest are text. Both are working in TestComplete at the moment.



    Has anyone else experienced this problem and is there a long term solution.