Forum Discussion
AlexKaras
11 years agoCommunity Hero
Hi Sanghamitra,
If you let us know what exectly you'd like to test, you might get more relevant piece of advice...
The case is that Load Testing usually assumes the check of how well the software functions when it receives a lot of external requests. Usually, this applies to the server software that runs on web server. Because of this, the most of the load testing software records and replays the network traffic (usually - http(s) traffic). LoadComplete tool by SmartBear does exactly this - it records http(s) traffic sent to some server and than replays it as if it was sent by a lot of separate users.
The same type of testing can be done for the software that handles TCP, UDP, or other traffic, but the software that supports load testing via these protocols is less widespread.
Alternatively, there is Concurrent Testing. This is when concurrent tasks are sent to the server software (for example, the request to delete and edit the same database record) and the goal of this testing is to check how well the tested software processes these concurrent requests. This type of testing usually does not assume too many requests to be sent, but instead the attention should be paid to the synchronous sending of these requests from separate computers. TestComplete supports concurrent testing via its Distributed Testing functionality as was mentioned previously by Tanya.
So, the answer to your question may vary depending on your actual needs.
If you let us know what exectly you'd like to test, you might get more relevant piece of advice...
The case is that Load Testing usually assumes the check of how well the software functions when it receives a lot of external requests. Usually, this applies to the server software that runs on web server. Because of this, the most of the load testing software records and replays the network traffic (usually - http(s) traffic). LoadComplete tool by SmartBear does exactly this - it records http(s) traffic sent to some server and than replays it as if it was sent by a lot of separate users.
The same type of testing can be done for the software that handles TCP, UDP, or other traffic, but the software that supports load testing via these protocols is less widespread.
Alternatively, there is Concurrent Testing. This is when concurrent tasks are sent to the server software (for example, the request to delete and edit the same database record) and the goal of this testing is to check how well the tested software processes these concurrent requests. This type of testing usually does not assume too many requests to be sent, but instead the attention should be paid to the synchronous sending of these requests from separate computers. TestComplete supports concurrent testing via its Distributed Testing functionality as was mentioned previously by Tanya.
So, the answer to your question may vary depending on your actual needs.