Kontrolery logiki i pętli

Welcome! In this lesson, we'll dive into Logic Controllers and Loop Controllers in JMeter. These powerful elements help you build more realistic and dynamic performance test plans.

They allow you to control the order and frequency of requests, simulating complex user behaviors beyond simple linear execution.

Logic Controllers in JMeter dictate the order in which user requests are processed. They add intelligence to your test plan, enabling conditional execution or specific sequencing.

• They act like "if-else" statements or "switch" cases in programming.
• Useful for scenarios where actions depend on previous outcomes or data.

Think of them as the brain of your test script, guiding the flow.

The If Controller is a fundamental logic controller. It executes its child elements (requests, other controllers) only if a specified condition evaluates to true.

• Purpose: Simulate conditional actions, like a user clicking a "login" button only if they are not already logged in.
• Condition: You define a condition using JMeter functions or variables, often a JavaScript or Groovy expression.

The condition for an If Controller is a powerful expression. It's often a boolean check on a variable or a response value.

For example, if you want to execute a request only when a variable userStatus is "new", your condition might look like this:

This tells JMeter to run the child elements only if userStatus is "new".

Loop Controllers are designed to repeat a set of actions a specific number of times, or indefinitely. They're essential for simulating repetitive user behavior.

• Purpose: Simulate actions like browsing multiple pages, adding several items to a cart, or performing repeated searches.
• They enclose sampler requests or other controllers that need to be executed multiple times.

When you add a Loop Controller to your test plan, you specify how many times its contained elements should run. You have two main options:

• Loop Count: Enter a positive integer to repeat actions a fixed number of times (e.g., 3 for adding 3 items).
• Forever: Check this box to make the loop run continuously. This is often used with a Thread Group's duration or scheduler.

Imagine a user adding multiple items to a shopping cart. Instead of duplicating "Add to Cart" requests, you can use a Loop Controller.

You'd place an "Add to Cart" HTTP Request sampler inside the Loop Controller, setting the loop count to, say, 5. This efficiently simulates adding 5 items.

Each iteration of the loop can use different data (e.g., from a CSV Data Set Config), making it very dynamic.

JMeter allows you to nest controllers, creating sophisticated test flows. You can place a Loop Controller inside an If Controller, or vice-versa.

• Loop inside If: "If user is premium, then loop 5 times through a special offer."
• If inside Loop: "Loop 10 times through browsing items, and if an item is a 'featured product', click on it."

This nesting capability makes your test plans incredibly flexible and realistic.

To get the most out of Logic and Loop Controllers, consider these best practices:

• Keep conditions simple: Overly complex If Controller conditions can be hard to debug.
• Use variables: Store dynamic values in variables and reference them in conditions or loop counts.
• Don't over-nest: Too many nested controllers can make your test plan difficult to read and maintain.
• Add comments: Explain the purpose of complex controller structures.

Great job! In this lesson, you learned about two essential JMeter controllers:

• Logic Controllers: Like the If Controller, they enable conditional execution and manage the flow of your test plan.
• Loop Controllers: They allow you to repeat actions a specified number of times, simulating repetitive user behaviors efficiently.

Mastering these controllers is key to building advanced, realistic, and robust performance tests in JMeter. Next, we'll explore Assertions!