Description
Behavior of using this element:
· In Random Order Controller it will execute each child element at most once. But the orders of execution of the samplers are random.
Category of the element:
This category of the element is Controller.
Where to use?
These elements can be used on thread group level and we can add this element in the workbench.
Business Scenario:
If a user wants to access different actions randomly in such scenarios we can use this random order controller.
Where not to use?
We can’t use this element in test plan level and test fragment.
Reason where not to use:
This element can’t use under test plan level because the scope of the controller is the thread group level. Thread group is a child of the test plan.
Constraints of Using this Element in test fragment
Test fragment is used to reuse the given samplers “n” number of times, whereas with module controller we are making a call to reuse the samplers from test fragment.
Here the criteria are placing the random order controller in test fragment results in a random execution of samplers.
But if our execution is in a sequential order sampler by sampler, in those cases we should not use this controller, which results to invalid execution.
How is it different from Random Controller? Highlight clearly?
Random Order Controller
|
Random Controller
|
In random order controller, it will execute all the samples in a random fashion.
|
In the Random controller, it will randomly pick one sampler and executes it randomly.
|
Below are the detailed explanations of both controllers.
No comments:
Post a Comment