Script conversion takes several minutes.

Question

As a general practice, we would like to convert all of our keyword tests to scripts. Most conversions just take a few seconds at most. However, some take several minutes to compile. The resulting scripts are only ~120 lines, including the comments, so these are not very large keyword tests.

What might be causing the conversions to be so slow?

Thanks.

clay · Accepted Answer

I decided to remove all of the visualization images from my keyword test. Now the script conversion is almost instantaneous rather the 10-15 minutes. I do not understand why the image snapshots would have such an effect on the script conversion, but the impact is apparently huge. Perhaps TestComplete developers could fix this??

Thanks to all for the help.

cunderw · Answer

Can you give a little more info? What at the differences in your KWTs? Are there a lot more parameters? Visualizer images?&nbsp;

clay · Answer

We don't use parameters very often.&nbsp; Our script building approach is to first map out the procedure using the recorder with the visualizer turned on.&nbsp; Then we step-by-step refine the recorded steps, adjusting the name maps and trying to use coordinates localized to the objects and etc.&nbsp; As we refine, the number of images goes down because we are replacing recorded steps.&nbsp; The last step is to convert to script&nbsp;I guess that means there are a lot of visualizer images, but from key word test to key word test I don't think one has more than another.

marsha_r · Answer

Do the longer ones happen after you've been working on them for a while or randomly during the day? &nbsp;If they're always towards the end, I would suspect a TC memory leak. &nbsp;

clay · Answer

This is not a problem that gets worse.&nbsp; The first time and every time I try to convert certain scripts it takes several minutes to compile.

tristaanogre · Answer

Without more detail about what is in the KWT that take a few seconds and what is in the ones that take minutes, not much we can do. &nbsp;We'd probably need to see the actual KWT and everything that goes along with them to make the best evaluation.
&nbsp;
It's possible someone from SmartBear would know more about the processing that goes into that conversion and what could cause differences. &nbsp;But they, too, would probably need to know more about the test cases you're working with to give you a clear answer.&nbsp;
&nbsp;
My best guess is that there is something that is in the test cases that take a while that needs extra processing when going through the translation to script code. &nbsp;Test cases that are simply "click, keys, settext" on onscreen objects probably translate a lot easier than conditional statements, while/for/do loops, etc. &nbsp;The simple actions are a straight call to the syntax engine of the language. &nbsp;The other code is a bit more complex since each language has it's own way of syntaxing such loops. &nbsp;
&nbsp;
Just a guess, but that's where I'd start looking.

Forum Discussion

Script conversion takes several minutes.

8 Replies

Related Content

Hiptest Conversations

Add minutes to current date time using groovy

Forced Conversion

Play .pjs with several computors.

Implement several different endpoints in a single environment

Recent Discussions

Dynamic Object

Pulling in Dynamic Links from a web page

Multiple execution of a test plan with different values from an Excel table

Your thoughts about a REST API in TestComplete

Keyword Test - Click - use -1, -1 by default?