What is the simplest test plan in JMeter? It is a single Thread Group that contains both the HTTP Sample Requests AND the View Results Tree at the end of test plan. But is it a good test plan? Umm...that would be a definite no. Why? Because we said so. Just kidding, because in this case, JMeter will send requests one by one without any pauses in between.
Not too long ago, in a galaxy that has a delicious candy bar as its namesake, we came face to face with JMeter 2.7. Since it's a tad surprising to come across a new release so soon after JMeter 2.6 entered the realm, we decided that an exploration of V2.7 was needed. So onto the testing mothership (BlazeMeter's load testing cloud) to discover the newest features.
Ok, what's the bottom line: Why do we run load tests? For fun? (well, sometimes, load testing IS pretty cool.) We perform load and performance tests to make certain that our hard work designing, programming, building and creating websites and applications do not fail when they go live. We need to ensure that these apps and sites are ready to be deployed on a production server, that they can handle the varying loads or influx of concurrent users (aka traffic).
Are you a website administrator or owner? So, do tell, what do you think about the quality of your site performance? Superman speedy or sluggish-like-a-snail? Is it based on Drupal by any chance? If so, read on and completely change your relationships with the performance testing process. 1. Forget About Scripting JMeter is an awesome tool for performance testing. But it does require knowledge of scripting. So, what can you do if you need to run a load test against 1-3 pages?
BlazeMeter is proud to announce our first partnership, with Acquia, the enterprise guide to Drupal. Like the mystical forces of yin and yang, BlazeMeter and Acquia are complementary forces that interact to form a greater whole, as part of a dynamic system. And our combined forces create a new standard in the world of load and performance testing.