Skip to content
gpawade edited this page Feb 11, 2018 · 1 revision

JMeter

Test Plan

The Test Plan is where the overall settings for a test are specified.

  • Static variables can be defined for values that are repeated throughout a test, such as server names. For example the variable SERVER could be defined as www.example.com, and the rest of the test plan could refer to it as ${SERVER}.

1 Thread Group

  • A Thread Group defines a pool of users that will execute a particular test case against your server.
  • In the Thread Group GUI, you can control the number of users simulated (num of threads), the ramp up time (how long it takes to start all the threads), the number of times to perform the test, and optionally, a start and stop time for the test.

1.1 Sampler

  • Samplers perform the actual work of JMeter.
  • Each sampler (except Test Action) generates one or more sample results.

- HTTP Request

This sampler lets you send an HTTP/HTTPS request to a web server.

1.2 Assertion

Check on response

- Response Assertion

Failed test based on

  • Test Response
  • Status Code
  • Request Header
  • Response Header

- Duration Assertion

Failed test based on response duration

1.3 Listeners

  • The element that gather information about test
  • Used to view results/ matrix of test

- Summary Report

The summary report creates a table row for each differently named request in your test. This is similar to the Aggregate Report , except that it uses less memory.

- View Results in Table

This visualizer creates a row for every sample result.


WorkBench

The WorkBench simply provides a place to temporarily store test elements while not in use, for copy/paste purposes, or any other purpose you desire.

  • Tools available for Recording

    • Badboy