About BlazeMeter
Reviewing JMeter
We have worked with JMeter preparing scripts to simulate user actions. Now, it’s time to prepare test executions in BlazeMeter to simulate larger scenarios. It’s very important that all JMeter concepts are clear. Let’s review the most important JMeter elements, focusing on the scope and structure.
In our scripts we want something like the structure shown in the following image (taken from here):
In this script each request has its own HTTP Header Manager and Response Assertion, applied only to the corresponding request. In some cases, requests can have a Regular Expression Extractor.
The JMeter test tree contains elements that are both hierarchical and ordered. Some elements are strictly hierarchical and some are primarily ordered.
In this test plan, we created a list of sample HTTP Requests. These requests are organized within Transaction Controllers. Both HTTP Requests and Transaction Controllers are ordered, therefore the order of the requests will be, 1, 2, 3, 4, 5 and 6.
Elements like Response Assertion, Regular Expression Extractors and Timers are hierarchical. So, after JMeter executes the HTTP Request 1, it will execute the Response Assertion 1 and the Regular Expression Extractor 1. This behavior is the same for all HTTP Requests.
If we have a test plan like this:
Then Assertion #1 is applied to Request One and Assertion #2 is applied to Request Two and Three.
If a hierarchical element is applied to a controller, then this element will be applied to all the elements inside said controller. Timers are inside a Simple Controller so that the timer executes only once. These Simple Controllers are between the Transaction Controllers because they represent the time that users spend thinking or filling out the forms on the page and each Transaction Controller contains all the HTTP Request sends in each action.
Timers are also hierarchical and if we do something like in the following example, then Timer #1 will apply to Request Two, Threeand Four and Timer #2 will apply to all Requests.
About BlazeMeter
JMeter is one of the best open source performance testing tools available on the market today, but no tool is foolproof and there are always pros and cons to be found with each one.
If we want to excecute a performance test using JMeter, depending on the script, we can probably execute around 500 users with the load generator. In our experience, sometimes we can execute a few more users and other times we can only execute less than 100.
With JMeter we can distribute the load between various generators. In this way, if we wanted to simulate 1,000 users then we could use two generators, each one executing 500 users.
This is a good solution if we have a small load to generate, but if we wanted to generate 10,000 users then we would have to use 20 generators, which would be too expensive and complex.
What is BlazeMeter?
BlazeMeter is “JMeter in the cloud”. This means it’s not only 100% compatible with JMeter, but it also addresses it’s limitations like scalability, stability and reporting.
How does it work?
In BlazeMeter we can directly upload a JMeter script and execute it.
All we need to do is write the test-script or upload JMeter scripts, choose the amount of load-engines and run the test. BlazeMeter takes care of the everything else. An unlimited number of load-engines are pre-configured and available. Detailed graphical reports are generated during the load as well.
Benefits
- The ability to generate up to 1,000,000 (or even more!) virtual users — no need to worry about infrastructure cost and setup
- The ability to test from multiple geo-locations — no need to worry about test and report synchronization
- Real time monitoring and reporting
- Easy access to monitoring and reporting
- Easy access to historical reports for comparison
- The option to extend your test data further with top-tier APM solution integrations like New Relic and CloudWatch
- End-to-end visibility of your server, app (web and mobile), and end user experience
- “On-the-fly” script recording with the BlazeMeter Chrome Extension
- It’s a simple way to maintain and execute JMeter scripts from one location
- Real mobile device testing
For more information visit the official BlazeMeter webpage.
BONUS LECTURE: Must-Have Resources
Thanks for taking our course! Your feedback is highly important to us. Please take a couple of minutes to fill out our feedback survey here.
While you continue your performance testing journey, here are some other resources that we think will help!
- Our Performance Testing Blog has dozens of helpful articles with tips (don’t forget to subscribe!)
- Read our CheckList: 8 Ways to Improve JMeter Scripts