Ask a Question

PC Requirements

romanmfs
Frequent Contributor

PC Requirements

HI all, 

My TC been running slow lately, do you guys think these specs are good enough?

 

PC1: 

I5-2500 @3.3GHZ

8GB RAM

1TB HDD

 

PC2: (remote virtual machine)

 

Intel Xeon E5649 @2.53GHZ

8GB Ram

60GB SSD

 

 

Thanks

2 REPLIES 2
Marsha_R
Community Hero

Here are minimum requirements:

https://smartbear.com/product/testcomplete/specifications/

 

Here are some general tips to speed things up:

https://support.smartbear.com/articles/testcomplete/test-playback-performance-tips/

 

Has anything changed on your systems lately?  TC version?  Browser version?  Anything else?


Marsha_R
[Community Hero]
____
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
https://community.smartbear.com/t5/custom/page/page-id/hall-of-fame
tristaanogre
Esteemed Contributor

One of the things not mentioned has to do with a couple of NameMapping settings.

 

Under Tools | Options | Engines, there are two things that I would recommend turning off.

 

First, Uncheck "Search for visible objects first".  If you have code that checks for existence or other similar checks against objects that might not have the Visible property set to true, this can slow down playback.  Unchecking this has the search algorithms of NameMapping search all available objects which means that it will find such "invisible" objects faster, improving performance.  When we unchecked this, we saw a remarkable increase in performance on our systems.

 

Secondly, and this won't have such an immediate effect, uncheck the option "Use extended find when possible".  Having that option checked means that every time you map something in TestComplete, it will automatically collapse your components and use the "Extended Find" feature.  This isn't necessarily a bad thing but using Extended Find TOO much can slow down performance as, for each component that has that flag checked, the NameMapping algorithms execute a search of child objects to find the desired one which does slow down performance.  I uncheck that option and then only use "Extended Find" where necessary rather than letting TestComplete choose for me.

 

Now, if you had that second option checked and then uncheck it, as mentioned, this won't have an immediate effect.  In order to improve performance where Extended Find might be the cause, you will need to find all mapped components that have that flag checked and add additional "parent" components into your mapping tree in order to be able to turn that flag off.  This does take some time and elbow grease, however, once you do it, you will see improved performance.


Robert Martin
[Hall of Fame]
Please consider giving a Kudo if I write good stuff
----

Why automate?  I do automated testing because there's only so much a human being can do and remain healthy.  Sleep is a requirement.  So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.

Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available
cancel
Showing results for 
Search instead for 
Did you mean: