How Loadgen’s Assertion Mode Validates Elasticsearch Responses

Response Assertion

Loadgen allows users to assert server responses, ensuring that status codes, headers, body content, JSON bodies, and request latency meet expected criteria. The concept mirrors the C language assert mechanism, which aborts execution when a condition is false.

1.1 Assertion Example Configuration

A simple request configuration demonstrates how to use response assertions:

requests:
  - request:
      method: GET
      basic_auth:
        username: elastic
        password: pass
      url: http://localhost:9200/medcl/_search?q=name:$[[user]]
      assert:
        equals:
          _ctx.response.status: 200

In this snippet, the assert block checks that the response status code equals 200. The variable _ctx.response.status extracts the status from the response context.

Response header: accessed via _ctx.response.header.

Response body: accessed via _ctx.response.body.

JSON‑formatted body: accessed via _ctx.response.body_json.

Request latency: accessed via _ctx.elapsed.

1.2 Assertion Failure Handling

If runner.assert_invalid is set to true, any assertion failure causes Loadgen to exit with exit(1), guaranteeing that failed tests are not silently ignored. By default this flag is false, so failures generate error messages without terminating the test run.

Effect of Assertions

Conclusion

Loadgen’s response assertion capability provides strong support for performance testing. By flexibly configuring assertions, users can accurately evaluate Elasticsearch performance under high concurrency and ensure system stability and reliability. The feature not only improves testing efficiency but also offers developers a better debugging experience, ultimately helping to raise application quality and user satisfaction.