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.
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.
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.
