I'm still having major performance issues with TestExecute.
I raised this thread:
http://smartbear.com/forums/f81/fp3/t88833/huge-performance-hit-using-testexecute-10-10/And opened a support ticket. But that didn't come to much. I was asked to send in my entire project which I can't do for commercial reasons.
So I rolled everything back to v10.0 and Chrome (which seems to be the worst affected) to v31. However, Chrome v31 did not seem to be very stable and would crash frequently. However, after tweaking the project settings as far as possible, I did get it running at a good speed. But with the constant Chrome crashes, the test was not reliable.
Finding older Chrome installers is a nightmare. So I saw you had released v10.20 so I decided to try that with Chrome v34.
And the performance is now worse than ever.
Here are some timings:
TE = Test Ecexute
C = Chrome
TE v10.0 / C32 - untweaked project settings - Runtime = 1hr
TE v10.10 / C34 - untweaked project settings - Runtime = 2+ hrs
Rolled back
TE v10.0 / C31 - tweaked project settings - Runtime = 17 mins (but with crashes in Chrome)
TE v10.20 / C34 - tweaked project settings - Runtime = 4 hrs 20 mins !!!!!!!So performance has gone way, way, downhill again.
Nothing changed between the last two runs listed except for updating TE and Chrome. The VM running all this is running Windows Server 2008 R2 64 bit. Xeon E5-2670 CPU. 2gb of RAM.
My initial thought was 2gb of RAM is not enough. So I left a perfmon trace running and RAM is only topping out at about 50%/60% peak used during the run.
As far as I can tell, TestExecute after v10.0 and Chrome v33/v34 are unusable.
My best option looks like reverting back to TE v10.0 (where I don't have any of these issues) but finding an installer for an older version of Chrome seems to be virtually impossible.
If anyone can point me to a stable v31/v32 install. That would be a HUGE help. The installer I have which does not appear to be stable is v31.0.1650.63. I've tried FileHippo but they don't actually host the older installers. It just directs you back to the Chrome site where the newest version is installed. Personally, I hate the way Chrome don't seem to make older installer available, but we appear to be stuck with it.
For the moment, I'm going back to trawling to try and find a stable Chrome v32 installer ....
Alumni