BlazeMeter Reviews

We use BlazeMeter for performance testing.

BlazeMeter helps us to easily scale up the products for performance testing and increases the scalability of the applications, which are outside of the corporate network.

The user interface is good. The multitask user and cloud missions testing are nice features.

The scalability features still need improvement. They have recently added dynamic user features, so we should evaluate that, which may enhance scalability. Storage capacity should be increased. 

There is a shared file repository with a limit of 999 file storage along with each payload, which is a maximum of fifty MB. That should be increased. When we run JMeter scripts in BlazeMeter, the BlazeMeter user interface does not recognize the property files we use in JMeter. This needs to be addressed.

I have been working with BlazeMeter for five years.

BlazeMeter's scalability features need improvement. They have added the dynamic user feature recently, and we should evaluate this feature for better scalability.

The technical support is very good. I would give them ten out of ten.

Positive

I have worked with LoadRunner and BlazeMeter simultaneously.

BlazeMeter's pricing is competitive but can be negotiable.

I have worked with LoadRunner simultaneously with BlazeMeter.

I'd rate the solution eight out of ten. 

I'm working for a telecommunications client. We are using BlazeMeter's Mock Services as a priority for performance testing, along with API monitoring. These functions are each used on different projects.

One of the projects for this client is completely based on Mock Services and, with the help of that functionality, we are able to complete end-to-end testing with all the dependent components.

There are third-company suppliers who provide components that need to be tested, but most of the time we do not get those components on time. Normally, we would wait until the development is completed and only then go for automation. But now, with the help of the Mock Services, once we get the source code, we upload it directly into the Mock Services and into the API monitoring. Once we get the tracers, we are ready to point to the actual instances and test things immediately. By the time we get to that stage, we are ready for the market. That means that even before getting the complete component, we can start working with something. There is no need to wait. As a result of the Mock Services, the time it takes us to develop API automation is minimized.

Also, we had a number of performance testing tools, but we had to integrate third-party applications for generating reports. That was a pain point for us when it came to showcasing things to stakeholders so that they could be aware of what was happening. But now, everything is available once the performance testing is completed. We can immediately see the reports, and when a test is running, I can share the execution page with anyone else, as a link. That means they can view exactly what is happening, moment by moment, regarding the response time, request time, and latency. That feature is not available in some of the other applications and possibly not in any of the other applications.

One of the areas that BlazeMeter benefits us is our test cycle times. In the past, if there was a defect with a component, we would have to wait until the issue was fixed. And even though we were not testing that particular component, because of the dependency of that component, we would have to wait until the issue was fixed. If it ended up going beyond the deadline for the release cycle, we would leave that test case for the next release.

With the help of the Mock Services, we are overcoming everything. Wherever we are facing issues, whether they will be long term or temporary, by implementing the Mock Services we can bypass the faulty components that are not needed for our particular testing. In that way, we are able to reduce our cycle times. In addition, we have some physical devices and network devices in our testing. It takes a week to create physical devices in a virtual way. Instead, with the Mock Services we are creating them in a minute, and that helps our end-to-end testing to be completed on time. The benefit of BlazeMeter's Mock Services is that it takes us through our testing early in the cycle.

In a single line of business, in a particular call flow, if we have 1,000 test cases per release, 100 to 200 of them are with the help of the Mock Services. That saves us time, money, and manpower.

And before we had BlazeMeter's API monitoring, if there were 10 components and anything was down, we would not be aware. We would not send a heartbeat every second to all of the components to check whether they were down or up. The API monitoring is a real benefit for us because we are able to schedule it for every 30 minutes or every hour, and we can keep on monitoring a component. If there is a failure, we will immediately be notified by email, even on the weekend. We can take action and report the situation to the data analyst and to the component people so that they can immediately work on fixing it.

The API monitoring is one of the most excellent tools we have come across because of the scheduling and the results. We are able to analyze how stable a component is based on that monitoring.

The most valuable features for us are the API monitoring and the Mock Services.

Another good thing is that we can upload JMX files and schedule and monitor performance testing. We are able to share results and see reports that we can't get in JMeter. In that way, the performance testing is good.

In terms of the range of test tools, when there are API calls we can do automation testing, functional testing, performance testing, and use the Mock Services to create a situation that the APIs are down. We are able to handle everything that has to do with APIs. Whatever we have to test—the functionality, the behavior—we are able to do so with the help of BlazeMeter.

One problem, while we are executing a test, is that it will take some time to download data. Let's say I'm performance testing with a high-end load configuration. It takes a minimum of three minutes or so to start the test itself. That's the bad part of the performance testing.

I don't think they can reduce that time because that's the functionality they have implemented in our BlazeMeter performance testing. But it's a pain point whenever we are running performance testing in a call or a demo, as well as in our live testing when all the business people are there.

The first time I run a given test, if it takes three minutes to download onto my server that's understandable. But every time I rerun the same test, it is downloaded again, because once the test is completed the files that were downloaded are removed. That means I have to wait for three to four minutes again.

We also had a call last week regarding secret keys. In JMX we have some Backend Listeners, such as Kibana, and there are usernames and passwords for them that we have to manually enter. When we upload the JMX file into BlazeMeter for performance testing, the usernames and passwords are viewable. Anyone who has access to BlazeMeter can download the JMX file and the usernames and passwords are visible to all those people. That's an issue with the performance testing.

Also, all the competitors have MQ protocol support, which is lacking in BlazeMeter's Mock Services. Having MQ protocol support in the Mock Services would be great for us. JDBC, the database communication, is also lacking. If we had those things, we would be completely satisfied with BlazeMeter's Mock Services. 

And for the API monitoring, we are missing a data-driven approach. If, for a single API call, we have 50 to 100 test cases, there should be no need for us to create multiple steps or to duplicate the test steps. Instead, if we had a data-driven approach available, we could directly add the test data into an Excel sheet and call it into the single test steps and achieve what we need to do. We have raised this concern to the Perforce team as well, and they said they are working on it.

I've been using BlazeMeter for two year.

It's stable. Sometimes we do face issues, but they are understandable things.

Every month or two months, something will happen in the back end. The UI will say, for example, that performance testing is down due to this or that reason, and that they are fixing it. Sometimes it affects our testing. We will be in a demo or in a call with our stakeholders where we are presenting and something will be down.

We will raise a support ticket and they will say they are analyzing it and fixing it. They won't take much time, but at that time, it's a pain point. But it happens in all tools. Because it is a cloud tool it's expected, but it's not happening very frequently, so we are happy with it.

We have weekly calls with the BlazeMeter support team, and that's a great thing. During those calls they will ask if there are any issues and whether we need something resolved. If we raise any concerns, they immediately help us during that call. If not, they will ask us to raise a ticket and they follow up on it on both sides—on the support side and with us. They will give us updates. I haven't seen any other companies do that. I have been amazed with the basic support.

We also get weekly updates on whatever the roadmap contains and the new features they are going to be implementing. If we have any doubts we address them in the call. We are using some other tools, but we haven't seen this much support from any other company. When it comes to support, Perforce is the best company I have ever come across.

Positive

We haven't had a chance to use the cloud services because of security issues related to our company. We only use the on-prem server. But the cloud services are one of the best things about BlazeMeter when comparing it with its competitors.

We have older tools, like CA DevTest, that we are still using due to dependencies on JMX, MQ, and JDBC steps that are not available with BlazeMeter. With DevTest we are able to handle a lot of the custom extensions. Instead of the Mock Services, we were using the CA DevTest Service Virtualization tool. We want to move completely to BlazeMeter but we can't because of those dependencies.

Ca DevTest is the main competitor, but it doesn't have the performance testing available. Both solutions have pluses and minuses.

DevTest is hard to use. It has too many features for Service Virtualization. If a beginner is trying to learn something in DevTest, it's hard. It might take a month or two months to get some understanding of what the DevTest tool does. BlazeMeter is very simple. Even for beginners, they give some options in the Mock Services. If you're a beginner, you can create a Mock Service and it gives you a description for each and every step. This way, beginners can easily adopt BlazeMeter.

In addition to the step-by-step demos, there is the BlazeMeter University. When we onboard people into BlazeMeter, we ask them to go through those courses. For example, if we are asking them to work on API monitoring, we have them do the course on API monitoring. Once they get the certification, we have them work on the API monitoring. With the BlazeMeter University, there is no need for us to have a separate KB on how it will work or how it will respond. Onboarding people into BlazeMeter is not a problem for us.

We were using the functional testing for APIs, but it has been disabled in our organization. I asked what was the purpose of disabling it and they said it was to make sure that everyone is using the API monitoring. Although we requested that they enable it again for our purposes, so far we haven't had much chance to explore the API functional testing.

Overall, I would rate the solution at seven out of 10 because I have sent some requirements for API monitoring and performance testing on Mock Services separately, to separate teams; things that should be introduced into BlazeMeter. Until those things are available, I am not able to use some of the components 

The solution’s most valuable feature is the dashboard.

BlazeMeter does not provide integration with the Aternity tool. The solution has the capability to work with Dynatrace, AppDynamics, and New Relic. However, it does not have the option to integrate with Aternity.

I have been using BlazeMeter for the last one and a half years.

I rate the solution’s stability an eight out of ten.

Around 800 users use the solution in our organization.

I rate the solution a seven to eight out of ten for scalability.

The solution's initial setup is straightforward and not time-consuming. It's easy to upload all scripts and everything we do on-premises to BlazeMeter. It is also easy to prepare whatever scenario we need.

We pay a yearly licensing fee for the solution.

Around 1,500 technical staff are needed for the solution’s deployment and maintenance. We mainly use BlazeMeter for performance testing and to generate the load from multiple locations. The automation and manual testing teams can also use the same tool for their automation testing or manual testing. So, BlazeMeter could be a single platform for multiple teams.

Overall, I rate the solution an eight out of ten.

We deliver it to the clients about the reports etc.

We have clients for whom we are upgrading their applications from old versions to new ones. Initially, we conduct assessments to compare the performance of the old applications with the new ones. For example, we might upgrade an application from a desktop environment to a web application. After the upgrade, we demonstrate how the new application handles load across the front end, API, and database. For this purpose, we use performance testing tools to showcase the improvements.

It is focused on concurrency testing, which has been especially beneficial for us. Their previous experiences had caused major setbacks. 

The pricing is high because the advanced version comes with different features. Unlike JMeter, which offers a free version, BlazeMeter requires you to upgrade to a higher tier to access those advanced features.

BlazeMeter comes with a cost, so our client must agree. We've settled for the basic plan, which limited our ability to explore the higher versions. This is one drawback, especially since JMeter already provides many features that are out of the box. However, a positive aspect of BlazeMeter is that it offers various options for capturing different formats, such as JSON, XML, etc.

I have been using BlazeMeter for seven months.

It is stable. It depends on the client's requirements. There's no hard-n-fast rule. We have multiple clients, and when they request it, we perform the testing for them. It's done once a week or once a month, depending on the needs. Unlike KN automation, it's not a regular process. We conduct performance testing primarily for assessment purposes and system improvements based on client requirements.

It is scalable but distributed, and everything comes with a price. We haven't explored much but expect to explore in the future.

We are around five to six people using BlazeMeter in our organization.

We are experiencing some delays with BlazeMeter, as running or executing tests takes a bit of time. For example, running a test with a hundred clicks for a conference user takes approximately twenty minutes. This is one of the issues we're facing. We're exporting from BlazeMeter and importing the test into JMeter for the KN to address this. 

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

We switched to BlazeMeter because of issues related to proxy handling in JMeter. BlazeMeter is more reliable in managing proxy errors, which was a significant reason for our transition. It also supports custom configurations, allowing you to define your own ports, etc. Additionally, BlazeMeter provides multiple options for recording and storing test scripts, which can be easily converted to UI or GUI formats. These features were the primary reasons for our switch to BlazeMeter.

The initial setup is not difficult. There is ready documentation and some videos to guide you.

It is a bit pricey, especially if you're primarily interested in its recording and script conversion features. However, you'll need to opt for the higher-priced plans to access advanced features like scalability and distribution, as these features aren't included in the basic version. Additionally, the resources available in the basic plan are limited compared to the higher tiers.

Report-wise, everything is good. However, the execution time is slightly higher compared to other tools.  Everything is consistent regarding recording, and I haven't encountered any bugs. However, the execution time is inconsistent. Sometimes, when I run the same script at different times, it takes longer to execute.

Overall, I rate the solution a seven or eight out of ten.

I used it for a couple of projects, but I don't actively use it now.

We use it for performance testing, volume testing, stress testing, and endurance testing.

We use it for EPS, web HTTP HTML, SQM, RabbitMQ, and sometimes ActiveMQ. So, it handles various testing scenarios for me. 

It has been most effective in managing large-scale tests. It saves the test execution files to the repository. The tool also has a distributing/executing model. You can create a JMeter script or YAML and then execute it using different infrastructure-related configurations.

Moreover, it can be integrated with tools like ALM.

Running from the cloud with load distribution, it exhibits load from different geo-regions. The best feature is generating loads from different cloud regions.

I find these features useful for my particular use case because I can't execute or generate the load within my infrastructure. With the cloud, I can rent on a pay-per-use model and execute the load with a massive number of users.

Sometimes, when we execute tests, the results calculated by BlazeMeter, specifically the response times for failed transactions, are incorrect. We've already reported this issue. If this could be fixed, BlazeMeter would be a much better tool compared to LoadRunner.

Currently, it incorrectly calculates response times for failed transactions, it provides data that isn't useful. We have to manually aggregate the data to get accurate values.

In future releases, I'd like to see BlazeMeter integrate with mobile applications and allow testing on real devices.

By testing on real devices, we could gather metrics related to CPU usage, memory, and battery consumption. This would give us a better understanding of how the application performs on actual devices and help us ensure there are no battery drain issues, high internet usage, or excessive CPU or memory usage. This would allow us to confidently certify that the application is optimized for real-world device performance.

I work as a centre of excellence, so I've been working with JMeter and BlazeMeter for almost nine to ten years. 

For only BlazeMeter, it would be five to six years. BlazeMeter doesn't have versions, but JMeter is currently on version 5.6.3.

I would rate the stability a ten out of ten. There haven't been any outages, so I'm satisfied with the stability.

I would rate the scalability a nine out of ten. It scales well. When the load generators get overloaded, it automatically distributes the load to new instances.

We don't very actively use it right now, but we have used it in the past two years. If we have the opportunity and the client is looking for a cost-effective tool, we would definitely choose BlazeMeter.

My experience with the customer service and support have been very good. 

Positive

We used LoadRunner. The cost was the main reason for the switch.

I would rate my experience with the initial setup a nine out of ten, with ten being easy. It was straightforward, I didn't had any issues.

• Deployment Model: It's a SaaS model, so it's already available for use. We only need to create and upload our scripts.
• Integration with existing CI pipelines: Once a new build is ready, we have automated pipelines that trigger a load test on the deployed build. It then provides a result indicating whether it's a go or no-go based on the configured SLAs.

Our organization maintains BlazeMeter, not me. I'm a performance architect who uses BlazeMeter to assess application performance.

The cost is low, so there's a definite return on investment compared to LoadRunner. 

There is no direct ROI because we still pay for the product. But think of it this way: if I spend $100 on LoadRunner but only $10 on BlazeMeter, then the ROI is essentially the $90 saved. That's how we look at it.

I would rate the pricing a three out of ten, where one is very cheap, and ten is very expensive. 

We looked at NeoLoad. Here, also the cost was the primary factor.

Overall, I would rate it a nine out of ten. For me, it's a good product. 

It's a good tool for automation testing and performance testing, especially if you're looking for a high-performing, highly scalable, and cost-effective solution.

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 use BlazeMeter for our WebApp Performance Desk. It helps me test web apps, APIs, databases, and mobile apps.

BlazeMeter's most valuable feature is its cloud-based platform for performance testing. It means you don't have to worry about having your own devices or servers when testing web applications, as BlazeMeter provides the virtual devices you need for realistic testing.

The only downside of BlazeMeter is that it is a bit expensive.

I have been using BlazeMeter for three years.

BlazeMeter has been stable without downtime, and any performance issues are usually linked to the tested application, not BlazeMeter.

The product is fairly scalable.

BlazeMeter's tech support team has been excellent, providing helpful and responsive assistance through chat and email whenever we needed it. I would rate them as a nine out of ten.

Positive

I have used LoadView and it is pricier and offers its scripting tool, but it is better in some aspects. While BlazeMeter primarily uses emulators for testing, LoadView utilizes actual devices and browsers, particularly for web applications.

The initial setup is not too complex. It mainly involves configuring IP addresses and server communication, but it is a basic process similar to other tools.

BlazeMeter is more affordable than some alternatives on the market, but it is still expensive.

I would recommend giving BlazeMeter a try because they offer competitive pricing, and you can negotiate for discounts. BlazeMeter is more affordable than other products on the market but uses emulators instead of actual devices, which might be acceptable depending on your testing needs and budget.Additionally, it allows you to carry over unused virtual users to the next subscription, which can accumulate and save you money. Overall, I would rate BlazeMeter as an eight out of ten.

We are using it to execute performance testing for our website and mobile applications, including e-commerce solutions, internet banking, and more.

Our applications are in a cloud environment and have a lot of users using them at the same time. We are looking to create a better experience for the users. We execute this kind of performance setting to establish a baseline for response times and we use it to reduce them.

We are both a customer of BlazeMeter and a partner that implements it for other customers.

It helps us to work faster when doing performance testing. Because we're faster, we can better use our resources. We have more capacity for our backlog.

We have better visibility into test metrics by managing the reports and dashboards that present the results of test execution. That helps us to evaluate the performance parameters that the application should achieve. It has been great seeing the results that we are achieving.

It has definitely helped us to implement shift-left testing. By doing performance tests faster and earlier in the process, we have the opportunity to prevent performance issues in production. That aspect is very good.

In addition, the Scriptless Testing functionality means we can build a performance testing team in which some members don't need to have extreme programming or development experience. We can create a mixed team that has professionals with great expertise and less experienced people so that we can prepare them for the future.

Another benefit is the ability to build test data on-the-fly. That helps us increase test coverage. It's one of the main functionalities that helps us with that. It has also decreased our test cycle times by almost 35 percent, but I do believe that it could be even more than that.

One thing that we are doing a lot with the solution, and it's very good, is orchestrating a lot of JMeter agents. This feature has helped us a lot because we can reuse other vendors' performance scripts that they have used with JMeter before.

It can also be used for both performance and functional testing of any application and we can manage different kinds of data to better cover the performance and functional testing of the applications. For example, if we need different kinds of data to test the different uses of an application, we can use this platform to help us with that. 

Another thing we like is that while it's difficult sometimes to connect this kind of performance test solution with application performance monitoring solutions, BlazeMeter has been great. Our experience with that has been great.

BlazeMeter is the perfect tool for us because it works with cloud and open source and other vendors' solutions. It's very good with other testing solutions in both our and our customers' ecosystems. For example, it's very good for perfecting mobile solutions and with other test data management solutions. It's very easy to integrate it into the software testing processes and tools that our customers are using.

It's also very good at bridging Agile and CoE teams. One thing that we are exploring right now, to make sure it works correctly, is the integration of BlazeMeter in the continuous integration and continuous delivery journey.

I believe that data management and test server virtualization are things that Perforce is working on, or should be working on.

I have been using BlazeMeter for three to four years.

I don't recall having any issues with its stability. I'm extremely satisfied with that.

The scalability is great. We can have a lot of virtual users when we need them.

We use BlazeMeter in different environments because we have customers with on-prem and cloud solutions.

I'm very happy with the technical support. They have answered all our needs.

Positive

We went with BlazeMeter because we can easily access the platform through the internet and because it is very easy to incorporate it into our processes.

The return on investment is guaranteed with BlazeMeter. If you only look at the price, you will only see one side of the financial equation. We like to evaluate the return on investment in terms of reduced testing time, increased productivity, and the ability to deliver many more features into production with BlazeMeter.

I've worked with other performance testing, service virtualization, and test data management solutions. I have been working in the software testing area since 2000.

People love using JMeter, which is an open-source solution, but I prefer BlazeMeter because we can easily orchestrate a lot of testing. It has additional features that help make our performance and non-functional-requirements testing better, because we can integrate it with functional testing. And there are service virtualization and test data management features in the same solution. In a good number of cases, we only need BlazeMeter to do many things, rather than using two or three tools to do the same job. It's a single workplace where we can do many things.

My advice would be not to look only at the price as the only point of decision. Evaluate if the tool is a good fit with your business and challenges.

We are using the SaaS solution. For companies that want to start, it's a better approach because it's easy to use: Pay and go. Of course, in large accounts, we are facing companies that are looking not only for cloud and private cloud, but for hybrid solutions where it is installed on-premises and in the cloud. BlazeMeter is up to this kind of challenge.

Adoption is a challenge that we face with every new tool or process. Because BlazeMeter is easy to use, we can adopt it faster. For developers and Agile teams, it's very helpful when we can use something quickly. That has helped a lot in the adoption.

The level of maintenance is okay. It is nothing that would create barriers for us. We have a team of eight people involved in the solution, and their roles include administration and performance testing.

Blazemeter is one of the top-three that I have found. It doesn't have any negative points compared to others.