HTTP Request Samplers and Assertions

Most JMeter performance tests focus on HTTP APIs or web applications, and HTTP Request samplers are the core mechanism for sending those requests. To get useful results, you must configure paths, parameters and assertions that validate responses under load.

Configuring HTTP Samplers and Assertions #

An HTTP Request sampler specifies the method, path, query parameters, body and headers for a request. Assertions, such as Response Assertion or Duration Assertion, let you define what success looks like—for example, specific status codes, response text or maximum response time.

<HTTPSamplerProxy testname="GET /api/products" enabled="true">
  <stringProp name="HTTPSampler.domain">api.example.com</stringProp>
  <stringProp name="HTTPSampler.port">443</stringProp>
  <stringProp name="HTTPSampler.protocol">https</stringProp>
  <stringProp name="HTTPSampler.path">/api/products</stringProp>
  <stringProp name="HTTPSampler.method">GET</stringProp>
</HTTPSamplerProxy>

<ResponseAssertion testname="Check 200 OK" enabled="true">
  <collectionProp name="Asserion.test_strings">
    <stringProp name="0">200</stringProp>
  </collectionProp>
  <stringProp name="Assertion.test_field">Assertion.response_code</stringProp>
</ResponseAssertion>

By combining well-configured samplers with meaningful assertions, you ensure your performance tests also validate correctness.

Common Mistakes #

Mistake 1 — Omitting assertions entirely #

This risks false confidence.

❌ Wrong: Measuring response times without checking status codes or content.

✅ Correct: Assert on status codes and key response fields to ensure the system behaves correctly under load.

Mistake 2 — Overcomplicating assertions #

This slows tests.

❌ Wrong: Writing very heavy pattern matches on full HTML or JSON when a simple check would do.

✅ Correct: Choose simple but effective assertions that match your success criteria.