Protocol Implementation > Protocol Add-on Overall Testing > Load And Stability Checklist |
Test the protocol's stability and ability to process load:
Perform the load and stability tests on all operating systems the protocol supports
Run a stability test for at least two hours, and for at least 1000 iterations with at least 50 virtual users. Verify that:
CPU usage does not exceed 75%.
The maximum increase of memory consumption per one virtual user in one iteration does not exceed 0.5%.
The transaction times are the same for a virtual user whether the stability test runs as a single virtual user or in the same process with other virtual users.
When virtual users are run as processes, the transaction times are the same for a virtual user regardless of whether other virtual users are running.
There is minimal thread interlocking. The transaction times are the same for a virtual user whether it runs as a single virtual user or in the same process with other virtual users.
There is minimal process interlocking due to accessing shared resources or any other cause. When virtual users are run as processes, the transaction times are the same for a virtual user whether or not there are other virtual users running.
Verify that the non-negligible process time on the client side during test run is reported as wasted time in the transaction
Verify that CPU and memory consumption do not increase when the script is regenerated more than twice. A small increase in system resource use between the first and second regeneration is acceptable, but resource use should not increase after the second regeneration.
Verify that exceptions are captured and handled