- Listeners show the results of the test execution.
- They can show results in a different format, such as a tree, table, graph, or log file.
- Graph result listeners display the server response times on a Graph.
- View Result Tree show results of the user request in basic HTML format
- Table Result shows a summary of test results in table format.
- Log show summary of test results in the text file
Aggregate graphs allow us to generate bar graphs easily and let us select graph display settings. The generated graph and table data can be saved explicitly in the form of PNG and CSV.
The aggregate report shows a separate table row for each differently named sampler request in the test.
Assertion Results display the results of assertions applied to the Sampler. You can see in the below figure if any assertion fails, it will look like this.
Please Note that Assertion Results SHOULD NOT BE USED during the Load/Stress test as it consumes a lot of resources like memory and CPU. It is recommended to use it with functional testing or debugging purposes.
View Results In Table:
View Results in a table creates and displays a row for every sample/request result separately. Please Note that View Results In Table SHOULD NOT BE USED during the Load/Stress test as it consumes a lot of resources like memory and CPU. It is recommended to use it with functional testing or debugging purposes.
View Results Tree:
View Results Tree displays a tree consists of all the Sampler responses along with their requests. Please Note that View Results Tree SHOULD NOT BE USED during the Load/Stress test as it consumes a lot of resources like memory and CPU. It is recommended to use it with functional testing or debugging purposes.
- Set up defaults and variables for later use by samplers.
- The figure below shows some commonly used configuration elements in JMeter.
CSV Data Set Config:
- Suppose you want to test a website for 100 users signing-in with different credentials. You do not need to record the script 100 times! You can parameterize the script to enter different login credentials.
- This login information (e.g., username, password) could be stored in a text file. JMeter has an element that allows you to read different parameters from that text file.
- It is CSV Data Set Config, which is used to read lines from a file, and split them into variables.
Let's understand this with an example :
- You used your browser (Firefox, IE...Etc) to browse www.google.com.
- You log in with your user and password.
- Your username and password will be stored on your computer as cookies.
- Next time, when you visit www.google.com, you don't need to do log in again because your browser will use your cookies as user data to log in.
- HTTP Cookie Manager also has the same feature as a web browser.
- If you have an HTTP Request and the response contains a cookie, the Cookie Manager automatically stores that cookie and will use it for all future requests to that particular website.
HTTP request default:
- This Element lets you set default values that your HTTP Request controllers use.
- You are sending 100 HTTP requests to the server google.com
- You would have to enter manually
server name = google.com for all these 100 requests
- Instead, you could add a single HTTP request defaults with the Server Name or IP
field = google.co
- No need to type 100 times!
Login Config Element:
- The Login Config Element lets you add or override username and password settings in samplers.
For example :
- You want to simulate one user login to the website www.facebook.com with user and password.
- You can use the Login Config Element to add this user and password set in a user request.
Difference between Config Element vs. the CSV data Config:
|Login Config Element
||CSV data Config
|Used to simulate one user login
Used to simulate multiple user logins
|Suitable for login parameter only (user and password)
||Suitable for large numbers of parameters