Forum Discussion

kirk_bottomley's avatar
kirk_bottomley
Contributor
11 years ago

TestExecute vs TestComplete Execution Speed

In our environment, I write the automations on one system, then we use our TE licenses to execute them on other machines (or I run it in TC on the machine they were written on). We are just now starti...
  • mtsmith's avatar
    mtsmith
    11 years ago
    Kirk,



    This is a long shot. Our distributed tests have been running slowly on the VM's. Performance metrics did not show much activity of interest and the symptoms were pretty much those of an I/O bottleneck. Monitoring TestComplete10 with Sysinternals Process Monitor showed a large number of calls back to the developer machine. Doing a DOS findstr on the workstation name in project files showed that the VM's were querying the developer station for performance metrics. Removing the metrics got rid of the problem.



    Of course, the VM's are still slow compared to workstation, but performance is much better in general.
kirk_bottomley's avatar
kirk_bottomley
Contributor
11 years ago
Identical, as far as make, model and OS.



I can't install TC on any other system. The TC license is node locked. The TE licenses are floating.



I tried running it on a TE license in a VM, and it took about nine hours. I figured it was a VM thing. When we tried running it on native hardware, it still took nine hours. The 90 minutes was conservative, too. I just ran it again using TE on the same machine as TC, it took 36 minutes.



The tests are run on a desktop application, on Windows 7. The test files are networked for all machines, including the authoring. The project location is also networked, for all machines. So in theory, any network lag should be the same even if it's run on the TC machine.



It could very well come down to a configuration difference, but the similarity between the VM and the hardware run time made me think this was an issue someone had seen before.