eBook > The JMeter Playbook: Build, Scale, and Optimize Performance Tests

Assertions

Assertions check the actual server’s response against anticipated values. If an assertion fails, JMeter marks the Sampler as failed, which increases the Error % in your reports.

Back to top

Response Assertion

The most commonly used and flexible assertion. Right-click a sampler → Add → Assertions → Response Assertion.

JMeter Screenshot: Response Assertion configuration.

📸 Screenshot: Response Assertion configuration.

Configuration

FieldDescription
Apply toMain sample, sub-samples, or both
Field to TestResponse Body, Response Code, Response Headers, or Request Data
Pattern Matching RulesContains, Matches (full regex), Equals, Substring, Not/Or logical operators
Patterns to TestOne or more strings or regex patterns

Example: Verify Status Code 200

Field to Test           : Response Code
Pattern Matching Rules  : Equals
Patterns to Test        : 200

Example: Verify Response Body Contains a Key

Field to Test           : Response Body (Text)
Pattern Matching Rules  : Substring
Patterns to Test        : "galaxy"

Example: Verify Response Does NOT Contain an Error

Field to Test           : Response Body (Text)
Pattern Matching Rules  : NOT Contains
Patterns to Test        : "error"
Back to top

JSON Assertion

Purpose-built for JSON responses. Right-click a sampler → Add → Assertions → JSON Assertion.

FieldValue
Assert JSON Path exists$.userId
Expected Value42
Match as regular expressionfalse

This asserts that the JSON response has a field userId with value 42.

Example: Assert Array Is Not Empty

Assert JSON Path exists : $.posts
Additionally assert value : (unchecked)

Check “Expect null” = false and “Invert assertion” = false. This simply asserts that the posts key exists.

Back to top

Duration Assertion

Fails the sampler if the response takes longer than a threshold.

Duration in milliseconds : 2000

Any response slower than 2 seconds will be flagged as a failure. This is useful for SLA validation.

Tip: By default, JMeter will wait for a response forever. So, if the system under test is overloaded and won’t respond, the Duration Assertion will never fire. Make sure to set reasonable connect and response timeouts, better in HTTP Request Defaults.

Back to top

Size Assertion

Validates the response size (in bytes). Useful for detecting truncated or unexpectedly large responses.

Size in bytes : 1048576
Type of comparison : < (less than)
Back to top

Assertion Scope

Like all JMeter elements, assertions follow JMeter Scoping Rules:

PlacementEffect
Child of a samplerApplies only to that sampler
Same level as samplers (under Thread Group)Applies to every sampler in the group
Under the Test PlanApplies to every sampler in the entire test

Tip: Place a generic Response Code = 200 assertion at the Thread Group level to catch unexpected errors on every request. Add sampler-specific assertions as children for body validation.

Back to top

Viewing Assertion Failures

Assertion failures are visible in:

  • View Results Tree - failed samplers are shown in red with the assertion failure message in the Assertion Results tab.
  • Aggregate Report / Summary Report - the Error % column reflects Samplers failures including the ones caused by failed Assertions.
JMeter Screenshot: Assertion failure shown in View Results Tree.

📸 Screenshot: Assertion failure shown in View Results Tree.

Back to top

Best Practices

  1. Always add at least one assertion. A load test without assertions cannot detect functional errors under load.
  2. Don’t add too many Assertions. Assertions have their cost and can consume load generator resources if overused.
  3. Keep assertions lightweight. Complex regex patterns executed thousands of times per second consume CPU.
  4. Use JSON Assertion for JSON APIs. It is faster, less fragile and more readable than regular expressions.
  5. Add a Duration Assertion to enforce SLA thresholds automatically.
  6. Check Error % in reports. A sudden spike in errors usually means the server is returning unexpected content.
Back to top

Summary

  • Response Assertion - flexible text/regex checking on any response field.
  • JSON Assertion - validates JSON structure and values via JSONPath.
  • Duration Assertion - enforces response-time SLAs.
  • Place assertions strategically using JMeter Scoping Rules to avoid duplicate elements and ensure that Assertion checks right Sampler result.
  • Always inspect assertion failures in View Results Tree when debugging.

Not let’s get familiarized with Logic Controllers which allow us to control the flow of our test execution.

Back to top