Jmeter From Scratch
- 1. JMeter An overview from Scratch By: Chinmay Kumar Brahma
- 2. Introduction to Performance Engineering Jmeter introduction Getting started with JMeter Overview of Process Flow in Jmeter. Best Practices for Test Execution in Jmeter.
- 3. Software Performance Engineering(SPE) is a systematic approach to build an application which will meet the Performance Requirements. Weapons for doing SPE: Performance testing Load Testing Endurance Testing Stress Testing Spike Testing Capacity Testing
- 4. Performance testing is a type of testing intended to determine the responsiveness, throughput, reliability, and/or scalability of a system under a given workload. The main focus for Performance testing is to create a Benchmark Behavior of the application and closely monitor the Performance of different resources. Here we are not focused to identify bottlenecks
- 5. Load testing is meant for constantly and steadily increasing the load to verify that Application Under Test(AUT) can meet the desired performance objectives specified in SLA(Service Level Agreement).
- 6. BIG Brother of Load testing. Endurance testing completely focuses on validating the performance characteristic of the product (AUT) when subjected to workload model and load volumes anticipated over a long period of time. Working on Weekends!
- 7. Stress testing focuses on determining application's robustness, availability and reliability under extreme condition: Heavy Load, High Concurrency, Limited computation resources and etc. Identify application’s behavior under extreme conditions and identify bottlenecks.
- 8. A subset of Stress testing. Spike testing is meant for repeatedly increase the load volume beyond the agreed upon production operation(SLA) for a short period of time and goes down after that. Main focus: Identify application’s behavior when it goes beyond the anticipated workload and reforms back.
- 9. This is like looking into the future. The objective is to determine the software application’s effectiveness in “scaling up” to support an increase in user load. It helps planning capacity addition to your software system. Capacity testing is conducted in conjunction with capacity planning, For example, to accommodate future loads, you need to know how many additional resources (such as processor capacity, memory usage, disk capacity, or network bandwidth) are necessary to support future usage levels.
- 10. Finding the Scalability, Reliability, Robustness of the application under test(AUT) at different conditions Analyze and Identify the bottlenecks for the AUT. Finding a way out to fix the issue make performance better. To Avoid It!!!
- 11. Open Source(Free Free Free !!!) 100 % Pure Java Protocol Supported: HTTP, HTTPS, FTP, SMTP, LDAP, JDBC, JMS, SOAP Distributed testing Supports many Cloud Based Load Testing Platform Blaze Meter, Amazon, Soasta Multi-Platform Support Write your own script GUI, Command line interface Data analysis and addition of Visualization plugins.
- 12. Install Java (6 or higher) Download Jmeter https://jmeter.apache.org/download_jmeter .cgi Add path of java installation in environment path variable.
- 14. Response Time Latency Throughput Ramp up/Ramp down Virtual User Bandwidth
- 15. a Start Send Request to Target server and Simulates number of User Server responds to the request Jmeter records all the Response from server Jmeter accumulates all data Finish Report Creation and Analysis
- 16. Test Plan: Everything under this node is going to be executed. WorkBench: Workbench is the node where we can put test element temporarily. Nothing under this node is neither going to be executed nor saved. Thread Group: It is going to serve as a bunch of Users(Virtual Users) and will be executed based on the test script. Listener: Listener is used to listen and process for suitable views/reports
- 17. Thank You