Skip to content
  • ZipCode Api
  • Blog
  • About RedLine13
RedLine13
RedLine13
Primary Navigation Menu
Menu
  • Start Testing
  • Demo
  • Pricing
  • JMeter
  • Partners
  • Docs
    • Documentation Home
    • AWS Set Up for load testing
    • AWS Approval for Large Tests
    • PHP, NodeJS, Python Load Tests
    • Scalability
    • Jenkins Plugin Setup
    • Premium Features
    • Knowledge Base

The JMeter Random Controller vs Random Order Controller

By: David Koziel

The JMeter Random Controller vs Random Order Controller

When it comes to introducing random variability within test plan execution, there are two similarly named plugins for JMeter which are up to the task.  Each of these applies randomization to your tests, but in different ways.  In this brief post, we will analyze the similarities and differences between the JMeter Random Controller and the Random Order Controller.

The Random Controller is one of two built-in logical controllers for randomization. When you add an instance of this controller to your test plan, you may nest multiple child elements (e.g., HTTP Requests) underneath this. Each time an iteration of your test plan runs, the Random Controller will select one of these elements at random and execute it. This is in contrast to the Random Order Controller. While the premise remains that child elements are added to this controller, each iteration of your test will run all contained elements. The order in which these elements are executed however will change each time at random.

Let’s consider the following sample test plan. Here we have added a Random Controller side-by-side with a Random Order Controller to explore how child HTTP Requests will be executed:

Sample JMeer test plan

On one iteration, the Random Controller will select either Sampler A or Sampler B for execution – but not both. On that same iteration the subsequent Random Order Controller will reorder the execution of both Sampler C and Sampler D such that either runs first, followed by the other. A series of three consecutive iterations of this test plan may yield the following execution ordering:

Request ordering for three consecutive iterations
Request ordering for three consecutive iterations.

Did you know that RedLine13 offers a full-featured, time-limited free trial? Sign up now, and start testing both controllers.

2023-10-02
Previous Post: Guest Post: SemperCon depends on RedLine13 for supporting their clients’ Load Testing requirements
Next Post: JMeter Assertions to Control Test Flow

Recent Posts

  • JMeter XML Format Post Processor
  • Order of Elements in JMeter
  • The JMeter Synthesis Report
  • Using the JMeter Plugins Manager
  • JMeter Rotating JTL Listener

Related

  • JMeter XML Format Post Processor
  • Order of Elements in JMeter
  • The JMeter Synthesis Report
  • Using the JMeter Plugins Manager
  • JMeter Rotating JTL Listener
  • Using Test Fragments in JMeter Tests
  • Step-by-Step Guide to Testing with JMeter
  • Functional Testing vs Performance Testing
  • A Gentle Introduction to Load Testing
  • Using the JMeter Counter Element

© RedLine13, LLC | Privacy Policy | Contract
Contact Us: info@redline13.com

Designed using Responsive Brix. Powered by WordPress.