Showing posts with label JMeter. Show all posts
Showing posts with label JMeter. Show all posts

Friday, January 12, 2024

How to Use Performance Testing Reports to Improve Performance

1. Statistics Summary
  • Maximum running concurrent users
  • Total throughput
  • Average throughput
  • Average hits per second
  • HTTP responses summary
2. Transactions summary
  • Total passed transactions
  • Total failed transactions
3. HTTP responses summary
  • The total amount of HTTP 2XX responses
  • The total amount of HTTP 4XX responses
  • The total amount of HTTP 5XX responses
4. Running concurrent users graph

5. Response times graph
  • The reports contain metrics and statistics described above, a list of issues (with description and links to the statistics section) that occurred during test execution, and a general conclusion about the application's performance.
  • The testing team prepares the reports after each iteration of the performance script execution and sends them to the Customer.

Wednesday, January 4, 2023

Performance Testing Real Time Examples

 Performance Testing:




Types of Performance Testing:



1. Load Test


2. Stress Test



3. Scalability Test


4. Soak Test


5. Load vs Stress



JMeter Works:


Thread Group


Thread count vs Loop count


Duration Assertion


Saturday, December 31, 2022

Introduction to JMETER and Performance Testing

 JMeter

  • JMeter is an open-source load-testing tool used by developers and performance engineers to measure the performance of web applications.
  • It can be used to simulate a heavy load on a server, network or object to test its strength or to analyze overall performance under different load types.
  • Measure the application performance and response times.


Test Plan: (Top level directory)
  • A complete test plan will consist of one or more Thread Groups, logic controllers, sample-generating controllers, Listeners, Timers, Assertions, and configuration elements.
  1. Adding elements.
  2. Removing elements.
  3. Saving test plans.
  4. Running test plans.
  5. Stopping a test plan(immediate shutdown), Shutdown(graceful shutdown).
  6. Logging the info and errors.
Important components of a Test Plan:
  1. Thread Group
  2. Listeners
  3. Timers
  4. Assertions
Thread Group:
  • The beginning point of any test plan.
  • The thread group element controls the number of threads Jmeter will use to execute your test.
  • All controllers and samplers must be under a thread group.
Main properties of thread group:
  • Set the number of threads (simulation of a number of concurrent users).
  • Set the ramp-up period (time taken to threads up and running = ramp-up period/Thread 
Samplers:
  • Samplers send requests to the server and collect the response.
  • JMeter supports several types of samplers, including HTTP, FTP, JDBC, LDAP and SOAP.
Listeners:
  • Listeners can be added to test plans or thread group level.
  • Listeners provide a way to view the results of a test in JMeter.
  • Listener options - Graph result, view results tree, view result table, aggregate report, aggregate graph, response time graph.