This is my first ever post on Performance testing and I am very excited to learn and share some very common and basic (also some advanced) informations on JMeter. I hope you all will enjoy learning this new series of JMeter.
The best thing about JMeter is, its
- Open Source
- Has most common load testing options which Loadrunner has
- Cloud execution support (Via commercial Blazemeter)
- JMeter Plugins with some out of the box options
- Fast, No code and easy to learn
For me, as a beginner in JMeter, I really love working with it and also there are lot of information available on JMeter in Apache JMeter website itself and you can find some more googling them.
So what are we going to discuss in this Series?
In this series of JMeter we are going to discuss on some of the
- Basic concepts of JMeter (Components)
Most common kinds of Stress testing plan
- DB Test
- Web Service test
- ASPX site test
- Data Driven parameterization
- Remote execution etc
- Analyzing performance report and using it for project
We will also discuss more on JMeter by touching some of its plugins and cloud based load testing using Blazemeter.
Introduction to JMeter
Well for new users like me, JMeter is an open source performance and load testing tool, which does testing of different protocols or types as shown below
- Web – HTTP, HTTPS
- Database via JDBC
- Message-oriented middleware (MOM) via JMS
- Mail – SMTP(S), POP3(S) and IMAP(S)
- MongoDB (NoSQL)
- Native commands or shell scripts
Most of the time we will be using JMeter to test Web applications only, which means HTTP and HTTPS protocol, hence most of the components (Which we will discuss later in this series) are focused towards web application testing. We will discuss all of them one by one later in this series.
Please leave your comments and Thanks for reading !!!