Forum Discussion
Hi Evgeny,
thanks for the quick help on the Async-Problem!
I have another question (also as issue posted in the past by me):
Opening the 'Select test'-Window in TC11 takes a lot of time to popup. Is it possible to load the units first, then select a unit, and after that choose a function from that unit instead of loading all functions of all units in the project?
We've installed TC/TE 12.3 and the problem still remains. Having a lot of sources with a lot of test-routines makes the dialog from which test-routines are chosen very slow...(> 1 minute for adding 1 new test is not ok)
Maybe you’ve got an idea.
Sincerely,
Paul Vinders
SOPTIM AG
installing Testcomplete 14 the problem still is there. The 'Select Test'-window appears after minutes because of the many routines in our project. But only a few dozen are real Testing-routines, the rest are utility-routines. Is it possible to select only the real Testing-routines?
sincerely
P. Vinders
SOPTIM AG, Germany
- AlexKaras5 years agoChampion Level 3
Hi,
> only a few dozen are real Testing-routines, the rest are utility-routines.
If those utility routines are not required for test routines execution then move them to the separate project.
If test routines cannot execute without utility routines, then consider your code base optimization, because it is not TestComplete, but underlying scripting language system runtime (JScript, VBScript, ...) which does not support dynamic code modules loading and require all scripting code to be loaded in memory and 'precompile' before execution.
- paulvinders5 years agoContributor
Hi Alex,
thanks for the reply. With Testing-routines I mean those routines that are the start of the test. The Utility-routines are called within the testing-routines, which do the actual work (build testdata, ui-testing, excel-work, destroy testdata etc), so required for the test and therefore in the project.
- tristaanogre5 years agoEsteemed Contributor
Routines are Routines in TestComplete. It doesn't distinguish between the two when it comes to running a script routine from someplace else.
Something you can consider is moving your utility routines into Script Extensions. That way they aren't showing up as "test" routines.