Bring Open Source to Your Company with BlazeMeter
Bring Open Source to Your Company with BlazeMeter
Check out how JMeter's open-source nature can provide a great option for your enterprise's testing needs.
Join the DZone community and get the full member experience.Join For Free
Are you looking for ways to manage your open source risk? We can help. Learn more.
Running load tests before big events and as part of your development strategy is crucial for ensuring your website or app performs well at all times. If you are a company, this is essential for high sales, positive brand recognition and satisfied customers.
There are many different performance testing tools to choose from, each with different advantages. Whichever you choose, we recommend you start with an open source performance testing tool. Open source tools are constantly developed by users so you can be sure they fit users' needs. Open source tools also have extensive community support and documentation, and they are free. Here is a guide to help you choose the right open source load testing tool for you.
Open source load testing tools can probably fit most of your basic needs. For example, let's take Apache JMeter. JMeter is the most popular open source performance testing tool, and for good reason. It has an easy-to-use GUI as well as scripting options with advanced scenario creation choices, its community creates plugins so it fits more testing scenarios, and it supports multiple protocols as well as any OS with Java.
What if JMeter fits most of your needs, but you still require additional features to be able to use JMeter in your company? For example, you might need the ability to collaborate with your colleagues on your tests and test results. This is out of JMeter's scope, as JMeter is a local tool installed on a machine and not a web or SaaS product.
BlazeMeter can leverage the existing open source tools available today, and complement their abilities with missing features. These include scalability, collaboration, advanced reporting, and integrations. Not for JMeter alone, but for around 20 well-known open source testing tools.
To use BlazeMeter, create your test in your favorite open source load testing tool (JMeter, Gatling, Locust, Selenium, etc.), save it and then upload your file script to BlazeMeter.
In BlazeMeter, you can configure the number of users, RPS limit, ramp-up, iterations and duration, just like in your open source test. The ability to easily ramp up the number of virtual users to millions with Blazemeter, by utilizing one of the ~20 performance open source tools supported, will help you simulate a scenario where you have hundreds of thousands of visitors to your website. A Black Friday scenario, for example.
Another advantage of running your tests in the cloud is the ability to run it from various locations. Let's say you have an app that is used around the world. By running part of the load from the East Coast, part from the West Coast and some from Europe, you can ensure you are simulating the real locations your users are coming from.
With BlazeMeter, running a highly complex, multi-geolocation test with multiple test cases can be easily configured and our powerful reporting will let you analyze the data and drill down to see how your system performs by location, test case, specific request label, and more. Results given on a trend-line and threshold alerts mean that you will be notified only about the tests that require investigation, as you set to performance test automation as part of CI pipeline.
After configuring and saving your tests — be it load, spike, stress, soak, API, regression, or functional — run them, and you will get results in just a few minutes. BlazeMeter provides advanced and insightful metrics in appealing interactive graphs, showing real-time KPIs like throughput, error rate, response time and percentiles. All tests are carefully stored with all their logs and artifacts, so a user can access full test information even months after the test ran. BlazeMeter's reports are more advanced and easier to use than open source reports, and are simple to analyze and understand.
In addition, all tests, reports and projects can be shared among colleagues and team members, unlike open source tools. BlazeMeter provides Workspaces and Projects, which enable adding users, assigning managers to performance tests and controlling users' privileges. These enable sharing assets, managing accounts, demarcating projects and collaborating on test creation. Since BlazeMeter is easy to use, it doesn't take much training for non-experienced users to start working on existing projects. Collaboration also shows managers who is working on what.
One of the most valuable ideas behind open source tools is the democratization of tools and knowledge. Instead of small teams clinging on to valuable resources, any developer, or person for that matter, can use these tools. The same goes for BlazeMeter, not only because it's easy to use, but because it makes the results accessible to non-technical audiences. Performance results can be exported as an executive summary, showing bottom lines, graphs and a glossary. This shows both the system's performance status and also the importance of performance testing systems, helping prioritize these tasks in Scrum sprints.
Performance testing, whether through Gatling, JMeter or BlazeMeter, is complete only as part of a larger Continuous Integration cycle. Continuous Integration ensures any new piece of code works well on its own and as part of your existing system. Therefore, BlazeMeter is compatible with Continuous Integration tools like Jenkins or TeamCity, as well as with APMs like CA APM and New Relic and Continuous Testing tools like Taurus. This can be easily configured through the BlazeMeter test dashboard, the command line or through the CI tools themselves.
Published at DZone with permission of Noga Cohen , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.