I primarily use the solution for performance testing. It can also handle capacity planning on web applications.
Silk Test is a tool with which we can simulate the number of users, and with that, ramp up and ramp down strategies that we can design. Based on the load model we can design performance tests for our applications. On top of it we can do configurations.
We test the solution to PPS. For example, we test how many PPS transactions per second will be simulated on Silk Test. We can find out how much time testing will take. You can integrate various performance tests, which typically takes one hour. We can do stress tests, and, within an hour, we can then test it. Sometimes, we help test the tool for as long as 36 hours to see how exactly the application can be implemented, in case of any memory loss.
When we did the applications related to performance, we design the load normally. When we try to understand the various critical performance test scenarios, using Silk Test, we record them. Afterward, we handle the configurations.
According to the results, we trigger. Once we trigger data, we try to observe the behavior of the application, as the tool now simulates the load. We look at the responsiveness and note that the response times are getting increased.
We also try to see what kind of behavior changes are happening within the application. We'll look at whether the hardware resources of the application are going up, or if memory is going down. We look for problems or memory loss.
Once we've finished testing, and observe everything, we'll try to do our engineering and work to uncover loopholes that may impact the application's performance. Everything will be recorded and investigated. We'll explain our findings to stakeholders and explain what needs to be done going forward.
