What is the purpose of distributed testing ?
Hi, I have TestComplete and one licence of TestExecute. TestComplete is on my physical computer. TestExecute is on a VM on the server, running in the night and sometime in the day. I have o...
Forum Discussion
I have a slightly different take on it.
For me, it's more about testing where scenarios require one or two computers/users/applications (delete as applicable) to be involved in a single test.
Or, for where you want to run things remotely in a test lab or such like.
I do performance test work as well and I have yet to hit a scenario where I would use a large volume of TestExecute machines to represent the user swarm. It would be a very expensive way of doing such testing! We often run scenarios with several thousand concurrent users. That would be a BIG chunk of cash required in license fees!
For web based stuff and network driven API's there is plenty of specialist load testing software out there. For desktop stuff, I would most likely use simulated versions/calls rather than multiple full scale installations of the AUT ....
...For example, LoadComplete as a load-testing tool? :)
For "load testing" desktop applications, usually the load is not in the application on the desktop but in the communications to databases, between server and client, etc. These are things that can be profiled using something like AQTime to look for performance problems, memory leaks, etc.
I'm with Colin_McCrae... I wouldn't use Distributed Testing for load testing... it seems to be intended and designed for multi-workstation test scenarios.