BlazeMeter Reviews

My company started to use BlazeMeter since we wanted parallel runs and more penetration across teams with more ease, allowing better reporting. BlazeMeter doesn't do anything on its own since it uses the same script used in JMeter. BlazeMeter serves as a tool for orchestration, and to arrange better testing, parallel testing, and better reporting, making it easy for developers to use were some of the factors that led my company to opt for BlazeMeter.

The most valuable feature of the solution is that I like its workspace and shareability of resources, allowing multiple people to access the same scripts and use them in different environments. The extensibility that the tool offers across environments and teams is valuable.

The tool fails to offer better parameterization to allow it to run the same script across different environments, making it a feature that needs a little improvement. The tool should offer some ease of use across environments.

The solution's scalability is an area of concern where improvements are required.

BlazeMeter was introduced a year ago in my new organization because we had a higher demand. My company is a customer of the product.

Stability-wise, I rate the solution an eight out of ten since my organization is still streamlining things at our end.

Scalability-wise, I rate the solution a seven or eight out of ten.

Technical support doesn't respond the moment you put up a query, so it takes time to get a response from the customer support team. The support team does respond with enough information.

I rate the technical support an eight out of ten.

Positive

I used mostly commercial IT tools in my previous organization, including JMeter.

The product's deployment phase is fine and is not difficult.

I can't comment on the time taken to install the solution since our organization uses a shared installation with our enterprise account. My team didn't need to actually install the product, so we just created our workspace, and that was it.

I rate the product's price two on a scale of one to ten, where one is very cheap, and ten is very expensive. The solution is not expensive.

Maintenance-wise, the product is fine.

Based on my initial perception and initial experiences, I rate the overall tool an eight out of ten.

BlazeMeter is a very good tool to add users and ramp up things, making them a few of its very good features.

BlazeMeter is a very handy tool requiring drag and drop to operate., but I don't think I can generate a JMX file unless I run JMeter, which is one of my concerns when it comes to BlazeMeter. In our company, we are mostly unable to capture logs or events with BlazeMeter. We want BlazeMeter to assimilate a mobile app, especially sincere company deals in mobile apps, and we wish to conduct testing using BlazeMeter. The solution has been good so far, but JMeter is one area that has been tricky for me since I cannot generate events.

I cannot speak about a particular weakness in the tool, but it is a tricky product since those who want to use it need to depend on another tool called JMeter. JMeter is required to get the scripts and JMX file before being able to run on BlazeMeter.

In our company, an APK is generated whenever we develop mobile apps, and when I drag and drop it as a script, a JMX file should be generated, which is a feature not included in the solution. The aforementioned area where the solution lacks can be considered for improvement.

I have been using BlazeMeter for two months. I am currently an end user of the tool using BlazeMeter's trial version.

It is a stable solution. When we compare BlazeMeter with other tools in the market, I can say that the solution's overall performance has also been very good in our company.

It is a scalable solution, but our company currently uses the tool's free version, and we have not opted for its paid version. Considering the aforementioned fact, I can't comment on the solution's scalability though I have heard from one of my friends that the product's scalability is good.

Around 50 people can use the product in my company.

In my company, we haven't contacted the solution's technical support since we are still exploring the product as we are a startup company. We are conducting a trial of all the tools available to us so that we can choose the ones that suit our company at the end of the process.

The tool's implementation is done since my company deals more in mobile apps than web apps.

My company is a health app provider making our process or business completely different in the market. We want a product that is not an API to test the performance of our company's apps, so we consider BlazeMeter to be a good option.

My company is looking for options, like LoadRunner tools, that can be a better choice than BlazeMeter.

My company needs to search for better options since we feel that we will have around a million users once we launch our health app in India. I want a tool that can help me test the app's performance, especially if a million users are using it.

BlazeMeter is a tool that is easy to use.

Interface and report generation capabilities make the tool very handy for its users. The only tricky area in the solution is running BlazeMeter on JMeter, an open-source tool making it a very complex part for me.

There are different technical stacks in the market in which one needs to invest. After the testing phase, one may go for an expensive product in the market. Once there is a stable product in the market and the company can generate revenue, then it is feasible to go for the paid version, which is an option available in JMeter, so I can recommend it to others. BlazeMeter's paid version can be a bit expensive compared to JMeter.

I rate the overall product a nine out of ten.

The use cases of BlazeMeter encompass a wide range of scenarios, including loop load testing for API-level, web service, or web application load testing. The primary purpose is to simulate various types of loads. For instance, if the load originates from distributed load testing, opting for a dedicated cloud solution would be advisable. This allows testing applications from diverse geographic locations and handling traffic from different tiers effectively. JAMITA cloud is particularly recommended for this situation, as it efficiently manages infrastructure interfaces and resolves technical intricacies associated with infrastructure maintenance.

It simplifies the process by emphasizing the key aspects of writing, uploading, and running scripts for testing purposes.

The most valuable aspect of BlazeMeter is its user-friendly nature, ability to conduct distributed load testing and comprehensive analysis and reporting features. It particularly excels in providing a clear and organized view of load test results.

BlazeMeter has room for improvement in terms of its integration with GitLab, particularly in the context of CI/CD processes. While it has multiple integrations available, the level of integration with GitLab may need further enhancements. It is known to work well with Git and Jenkins, although the extent of compatibility with GitLab is uncertain.

I have used BlazeMeter within the last 12 months.

BlazeMeter is a highly scalable solution. The solution is SaaS and the cloud vendor controls the scalability.

I have not used the support from the vendor.

The initial setup of BlazeMeter is straightforward.

I rate BlazeMeter an eight out of ten.

We use the solution for performance testing. We create the safe to upload to BlazeMeter. Also, we can do standalone and combined load tests depending on the requirements.

BlazeMeter is quite fast and can be accessed through the web browser.

We sometimes experience downtime, but not so frequently.

The product is stable.

I rate the solution’s stability a seven out of ten.

Customer support is fast.

Positive

We opted for BlazeMeter because it is accessible through the web browser.

The initial setup is straightforward.

Multiple people can focus on the same instance. If anyone wants to view the result, So it's quite easy. You don't need to share the GTL file. You can access the browser.

Overall, I rate the solution a nine out of ten.

I occasionally used BlazeMeter for load testing to get insights into log distribution and generate reports.

It is a good choice for people transitioning to cloud-based load testing tools and its most valuable features are its strong community support, user-friendly interface, and flexible capacity options.

Potential areas for improvement could include pricing, configuration, setup, and addressing certain limitations. Enhancements in data import/export and integration with other tools could be beneficial. Additionally, providing support for certain tools like Grafana, which some competitors offer, would be a good extension to consider.

I haven't noticed any stability issues with BlazeMeter so far. 

BlazeMeter's scalability for our company depends on the cost and our testing needs. It is a complex decision since it is all about how much testing we do, for how long, and what our budget allows. It is all about finding the right balance between our requirements and affordability.

I haven't directly used BlazeMeter's technical support, but I have found that their online resources and community are quite responsive. They have a strong presence on sites like Stack Overflow, with experts who provide quick assistance.

The initial setup is fairly simple. Deploying BlazeMeter is a quick process and it takes just a couple of minutes. You need to have an account with them, upload your test scripts from your local machine, and then configure and initiate the test.

Overall, I would rate BlazeMeter as an eight out of ten.

Whenever I am not able to record the script with the JMeter, I use BlazeMeter extensions to record the scripts. Whenever there is a need to execute something in the cloud, my company uses BlazeMeter.

There are some advantageous features that are available in BlazeMeter. The type of HTML reports that can be downloaded from BlazeMeter can be shown to the clients so that they can be provided with a clear picture in a clean way, allowing even a layperson to be able to understand the metrics our company shows with the help of BlazeMeter.

Whenever we use BlazeMeter for the ramp-up and designing the scenarios in our company, we also use JMeter or other load testing tools, which provide some convenience in areas where the granularity can be maintained in seconds. The ramp-up and ramp-down require our company to use the granularity for a few minutes, making it an area where improvements are required to be able to use the granularity in seconds. From a performance perspective, BlazeMeter needs to be improved.

Whenever we discuss the development stage, JMeter has plug-ins and other extensions in the area of WebSockets, and it is the same case in terms of the kind of extensions provided by JMeter that are available in LoadRunner. BlazeMeter has not found the extensions for WebSockets or Java Applet. Decoding the scripts that contain the applications with Java Applet is not possible with BlazeMeter or even with JMeter, and it includes some Oracle and desktop applications, too.

I have experience with BlazeMeter.

I didn't get much opportunity to work on the tool, but as per my experience, I can say that BlazeMeter serves as an alternate tool whenever my company faces some hurdles or challenges with the JMeter and k6. To record the scripts, I use BlazeMeter as an extension. With BlazeMeter, it is very easy to identify if a request belongs to an application or not, and in the initial phase itself, we can neglect the requests that don't belong to the application. In BlazeMeter, depending upon the requests, users can select a particular domain.

Though the product is scalable, I found the tool to be a bit tricky while setting up the scenario for the stress test and during step-up and step-down kind of scenario setup.

I have experience with Grafana and JMeter.

Whenever a comparison is made between JMeter and BlazeMeter, there are a lot of differences one can observe. With JMeter, our company has to concentrate on the features as it is an open-source tool that works with Java. The configuration of the systems should have some high-end configuration, and the heap size depends upon the load our company uses. JMeter can be used in UI or GUI mode or in a non-GUI mode. If users have to go with a smoke test and the preparation of scripts, the GUI mode of JMeter can be used. For the actual execution of load testing, we have to go with JMeter's non-GUI mode. With the non-GUI mode, until the completion of the test, I could see the percentage of the error, but I couldn't see what kind of error was there in the application. In JMeter, I had to wait until the completion of the entire test. When we use the BlazeMeter cloud as a licensed tool in our company, we do have to deal with the setup of any configuration area. With BlazeMeter, whenever our company executes the load test, parallelly we can monitor what kind of errors we get, and if possible, we can have a word with the development team in parallel and we can solve all the issues so we don't need to wait until the completion of the tests as some of them may be longer than thirty minutes to an hour. In current situations, everything works in the cloud, and every request and every click gets counted in the cost. In BlazeMeter, there is no need to wait till completion of the one hour or until the end of the testing phase. BlazeMeter provides better reporting, but it takes much longer to do so, making it an area of concern where improvements are required. It is not always sufficient to only use BlazeMeter.

The product's initial setup phase was simple.

The solution can be deployed in less than five minutes.

When compared with the cost of the licenses of other tools, BlazeMeter's license price is good.

Currently, I am looking out for Java Applet and Oracle applications. I want something that will support the load testing phase for the tools that Java Applet and Oracle support.

I rate the overall tool between six and seven out of ten.

Previously, to perform performance tests, we had to connect servers in the cloud, configure them to perform the test, and plot the results on a dashboard. BlazeMeter came to simplify all this work.

In terms of deployment, we are using local Linux servers (RHEL 7), and for the cloud, we are using EC2 servers with Amazon Linux. Our cloud provider is Amazon AWS.

With BlazeMeter, our main gains were in agility and efficiency in the execution of performance tests and delivery of post-test reports.

It has helped us to implement shift-left testing. It has certainly helped us to speed up the tests, and with that, we gained time to carry out tests in all development cycles.

It has the ability to build test data on-the-fly, and this on-the-fly test data meets compliance standards, which is very important for us. Real-time data helps us understand the behavior at each level of the test. So, we can define numbers that an application needs to achieve in the test to classify it as being OK or not. This data helps a lot in the real-time investigation. By looking at each level, we can identify the exact moment of degradation or “break”.

It decreased our test cycle times. I believe that we saved at least 50% of the time in preparation for the execution. Using BlazeMeter has greatly simplified our performance testing experience, especially the preparation part.

For me, the best part is that we can graphically see the test result at runtime. It helps us understand the behavior of the application during all stages of the test.

BlazeMeter is a cloud-based and open-source testing platform, which is very important for us because we can be sure that we're using a tool that follows market trends and stays up-to-date.

The Timeline Report panel has no customization options. One feature that I missed was not having a time filter, which I had in ELK. For example, there are only filter requests for a time of less than 5 seconds.

I have been using this solution for approximately 1 year.

It is very stable. We haven't seen any instability or unavailability issues so far.

It is scalable as per our needs. In our working model, the only team that uses BlazeMeter is ours. This solution is used only by our team whose mission is to bring performance tests to projects and squads.

They are very good. In the beginning, they held a workshop with our team, and whenever we ask questions, we are attended to without any problem. I would rate them a ten out of ten.

Positive

We didn't use any other solution. We performed the tests manually.

As soon as we got to know this tool, we realized how important it would be and the benefits it would bring to the company. Its main benefits have been gains in agility and efficiency. 

For the performance tests that we carry out in the company, we only use BlazeMeter. I don't know any other tools. My view of BlazeMeter is that it is a very mature tool that delivers what it has set out to deliver in an excellent way.

I was not involved in its deployment. In terms of maintenance, the only maintenance is setting up new servers for use. This configuration is usually performed by us in the Performance team.

I don't have access to the information about its cost. So, I can't say if we have seen an ROI and if we have reduced our test operating costs.

We did not review other products.

BlazeMeter brings agility and efficiency in the preparation and execution of performance tests. With this, we gain time which is used to increase the scope of tests and anticipate possible problems.

BlazeMeter didn't help bridge Agile and CoE teams because we have a specific team. So, there was no involvement of professionals who work with agile. We gained agility and efficiency, but there was no involvement of any external team.

I would rate BlazeMeter a nine out of ten.

I work in a bank where we use BlazeMeter to conduct our load testing or performance testing. In our company, we utilize multiple machines, and multiple projects are hosted on BlazeMeter.

The baseline comparison in BlazeMeter is very easy, especially considering the different tests that users can easily compare. The response time and the calls we make in our company are easy to trace with the help of BlazeMeter.

There is a tab in Blazemeter named Request Stats Report where improvements are required. If I have to go and find a particular timeline, which might be in a 15 or 20-minute window, there are no places or options where I can enter the perfect or exact timelines I want to find. You have the pointers to drag from one place to another, but that doesn't give me much freedom to get or find a timeline. Basically, on a tab in Blazemeter named Request Stats Report, there should be the start time and end time. In BlazeMeter's Request Stats Report, users should have an option where they can select and manually enter the test start and test end time to get the stats for a particular time period.

Scalability is an area of concern in BlazeMeter, where improvements are required.

I have been using BlazeMeter for a year.

The load testing time in BlazeMeter is too high since, in our company, we have seen that it takes four to five minutes to do an entire load testing process, and after that, we run the tests, which is a big problem for us.

Stability-wise, I rate the solution a five out of ten.

I see certain limitations when it comes to the scalability part of BlazeMeter since, in our company, we have faced multiple interruptions, because of which we had to stop certain testing processes.

Scalability-wise, I rate the solution a five out of ten.

I cannot give you an exact number related to the number of users of BlazeMeter in our company since we are just one of the teams in the company that uses the tool. I believe that around 150 to 200 people in my company use BlazeMeter.

I rate the technical support an eight out of ten.

Positive

I only have experience with BlazeMeter.

I rate the product's initial setup around seven on a scale of one to ten, where one is a difficult setup, and ten is an easy setup.

The time taken for the deployment of BlazeMeter varies since we have multiple types of applications in our company. If I have to deploy something on BlazeMeter, the time range for the deployment process can be somewhere between 30 to 120 minutes.

The solution is deployed on the cloud.

BlazeMeter is a supportive tool in terms of the fact that it is easy to migrate from one system to another. BlazeMeter offers an easy infrastructure that allows for migration, if needed, in a well-organized manner, but it is not an optimized tool yet since I still see a lot of problems in it.

I rate the overall tool a seven out of ten.