![]() Now you are ready and set to implement the controllers. ![]() Now add module controller & click on dropdown link. In this example we set Thread Properties as number of threads 1, ramp-up period 1, loop count 5 and 2 controllers that contains http requests. Right click on Thread Group > Add > Logic Controller > Module Controller Add module controller to thread group by using below steps. Module Controller provides functionality to run which module needs to run. In this example we set Thread Properties as number of threads 1, ramp-up period 1, loop count 5 and 3 http request on which we applied once only controller in one request. Right click on Thread Group > Add > Logic Controller > Once Only Controller Add once only controller to thread group by using below steps. Once Only Controller provides functionality to run any user request to run only once per loop. Right click on Thread Group > Add > Logic Controller > Interleave Controller Add interleave controller to thread group by using below steps. Interleave Controller provides functionality to run all user request in each loop and request in each loop will be in sequential order. Right click on Thread Group > Add > Logic Controller > Random Order Controller Add random order controller to thread group by using below steps. Random Order Controller provides functionality to run all user request in random order for each loop. In this example we set Thread Properties as number of threads 1, ramp-up period 1, loop count 5 and 3 http request. Right click on Thread Group > Add > Logic Controller > Random Controller Add random controller to thread group by using below steps. Random Controller provides functionality to run user request in random order for each loop i.e. ![]() Right click on Thread Group > Add > Logic Controller > Loop Controller Add loop controller to thread group by using below steps. Loop Controller provides functionality to run user request to specific number of times. Simple Controller doesn’t provide any functionality its just a container that contains user request. Now we implement following controllers on this above configuration & check what results we will get. Let take an example in which we have following configurations 1 Thread Group, 3 Samplers in Http Request form and 2 Listeners in table and tree form. With JMeter user can do testing other than load testing for example Stress Test, Functional Test, Distributed Test.To understand the use of different logic controllers in JMeter. ![]() So, basically what we did was we simulated 50 users accessing one API endpoint over 10 seconds (5 every second).Īs you can see it is pretty clear that its very easy to test the API with the number of virtual users with just a simple change in Thread Group configuration. So don’t worry about the result, if you have different values than mine. You might be having different results than me based on what your REST API endpoint does and based on other factors, such as geographical distance (which generally increases latency), the size of the requested item (which increases transfer time) etc. This is fairly a high value for a simple Rest API, but in my case, this endpoint does few heavy tasks and that is acceptable for me. Sample Time: The number of milliseconds that the server took to fully serve the request ( response + latency)Īccording to the View Results in Tree output, the load Time is 144.Latency: The number of milliseconds that elapsed between when JMeter sent the request and when an initial response was received.After that, the Sample Time (ms)and Latency columns are probably the most interests columns in the result set. We can see that the Status of all the requests in the above screenshot is “Success” (indicated by a green shield with a tick in it).
0 Comments
Leave a Reply. |