I would rate this solution 10 out of 10. 

We try to avoid scripting. We use the scriptless testing functionality about 95% of the time. With JMeter, you don't need a lot of scripting. I don't need to know a lot of automation or programming at this stage to use it.

We haven't faced any challenges in getting multiple teams to adopt BlazeMeter. I created a sandbox for my own team where they can experiment. People really wanted access to it, so I added more and more people, and the designers are now part of it.

For others who are evaluating this solution, my advice is to do the BlazeMeter University course first before you start to use the product. It will give you a general understanding of what it is. It only takes half an hour to an hour.

You don't always need to finish the course or pass the exam, but doing the course itself will definitely help. They have a JMeter basic and advanced course and a Taurus framework course. They have an API monitoring course, which will help for [Runscope], and one for mocks. Most of the courses are quick videos explaining what the product does and how it works. At that stage, you can go back and build your first automation test case on JMeter or [Runscope]. It's brilliant.

I would rate this solution a 10 out of 10.

I would recommend this solution for those who want to use it, but it depends on the need. My advice is that you can start using the tool immediately. There's no need to do POCs.

The intention of this tool is that people should uncover more and more in their testing. That means people should be doing more testing in an automated fashion, or they should just give a command to BlazeMeter, and it should execute test cases and give them some insight into whether something is wrong.

We want people to do more automation testing and move away from manual testing. That is the success criteria. That means that we are spending more on BlazeMeter, but that's a sign that we're doing more automation. Our operational expenditure isn't increasing because we still have a team to manage the BlazeMeter account and the on-premises setup.

Our intention isn't to save time. The ultimate goal is to increase the velocity and improve quality, which will happen if we uncover more defects early.

I would rate this solution an eight out of ten. 

It's a fantastic solution and can do so many things. But unless you have a team that's already very experienced with JMeter and BlazeMeter, there will be some ramp-up time to get people used to the new platform. Once you're there, the features and functionality of BlazeMeter will let you do things that were absolutely not feasible on your previous platforms.

We don't really leverage the actual test data integration and creation functionality, but we leverage some of the synthetic data creation. BlazeMeter will let you synthetically generate data for load tests, API, or mock services. We have leveraged that, but we have not leveraged some of the more advanced functionality that ties in with test data management.

The ability to create both performance and functional testing data is not very important to us. A lot of the applications we test are very data-dependent and dependent on multiple downstream systems. We don't leverage a lot of the synthetic data creation, as much as some other organizations might.

We don't extensively use BlazeMeter's ability to build test data on-the-fly. We use it to synthetically generate some test data, but a majority of our applications rely on existing data. We mine that in the traditional sense. We don't generate a lot of synthetic test data or fresh test data for each execution.

BlazeMeter hasn't directly affected our ability to address test data challenges. We don't directly leverage a lot of the test data functionality built into BlazeMeter, but we're trying to move in that direction. We have a lot of other limitations on the consumer side that don't really let us leverage that as much as we could. It certainly seems like a great feature set that would be very valuable for a lot of customers, but so much of our testing is done with existing data.

We haven't had any significant challenges with getting our teams to adopt BlazeMeter. There were just typical obstacles when trying to get people to adopt anything that's new and foreign to them. Once most of our users actually spent time using the platform, they really enjoyed it and continued to use it. 

There were no significant hurdles. Their UI is very well-designed and user-friendly. Perforce puts a lot of effort into designing its features and functionalities to be user-friendly. I've participated in a few sessions with them for upcoming features and wire frameworks of new functionalities.

BlazeMeter meets our needs well. It performs admirably for our purposes.

Overall, I would rate the solution an eight out of ten. I would recommend using this solution to other users. 

I rate BlazeMeter nine out of ten. There's still some room to grow, but it's a pretty solid product. If you're comparing this to other tools and you're thinking about using BlazeMeter for functional testing, take a look at the action groups, object library, and test data generation features. Those three things make your day-to-day work a lot easier. It simplifies creating and maintaining your tests. 

BlazeMeter offers options like test scope that provide visibility of what a user does. Moreover, the option provides users with a crystal clear outline of every step, which consists of things like what the request is for a particular response.

Considering its load-testing capabilities, I recommend BlazeMeter to those who plan to use it. It's a good tool that anyone can use either in their production environment or before entering the production phase. The tool performs well even with real traffic while providing good scalability options to its users.

I rate the overall tool a seven and a half out of ten.

I would rate the solution an eight out of ten. 

The solution enables the creation of test data for performance and functional testing, but our use is focused on performance testing. We don't particularly use functional testing, but we are currently talking about using test data management for functional testing. We have our in-house automation framework, so the ability to create both functional and performance test data isn't a high priority for us.  

We don't use BlazeMeter's ability to build test data on-the-fly, not because we aren't aware of it, but because we are still at the early stages with the solution. Until fairly recently, just one other person and I were in charge of performance testing for the entire company, so having self-sufficient teams is an immense change for us as an organization.

I would say it's critical to have the appropriate skillsets among the staff as we could deploy just about any solution in an enterprise. Still, it won't be used to its total capacity without the proper skills. BlazeMeter showed us how little performance testing we were doing before and how vital increasing that footprint is. We've onboarded 50 users; that's 50 users who were not engaged less than a year ago and can all carry-out performance testing.

This solution can work very well for enterprise companies with a more advanced skill pool to draw from. For beginners in this area, specific skills such as JMeter scripting are required to use the application. It's easier to use than most solutions but requires a particular skill set to deploy and operate successfully. A good solutions architect and QA leads are essential in evaluating any product.

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.

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 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.

I rate BlazeMeter an eight out of ten.

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.

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

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.

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.

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.

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.

BlazeMeter should release frequently updated demo versions of the solution to the market. They can let the internet community test it, such as crowdsourced testing, this would be good for them in the market.

I would recommend this solution to others if they have a small budget and do not have the option to buy another solution. Otherwise, Tricentis NeoLoad and Micro Focus LoadRunner are the best.

I rate BlazeMeter a four out of ten.

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 

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

I rate the overall tool a nine out of ten.

I have not integrated the tool with any other solutions.

Though it is a good tool, there are certain areas where improvements are required in the product.

Compared to BlazeMeter, multiple options are available in the market for people to choose from to meet their requirements.

I rate the overall solution a seven out of ten.

We're a customer and an end-user.

I'd advise a company considers multiple technologies to support its goals. 

I'd rate the solution at a seven out of ten.

BlazeMeter is an easy way to get really accurate results from JMeters that you already have without having to build a set of networked JMeters (e.g., one with the UI running a bunch GUI-less slave machines).

I recommend BlazeMeter because of the accuracy of the results. 

I rate the solution eight out of 10. 

Definitely ask your engineering staff if they're familiar with JMeter. If they're not, it would be good to get a quick two-hour tutorial on it and then BlazeMeter will make a lot more sense.

It is an excellent and reliable tool. I liked it very much.

If you are looking to improve your website performance and ensure maximum uptime by load testing your system from end to end, then there is no better solution that I have found. It is extremely simple to setup.

It's free and easy to sign up and try, so give it a whirl and see if it meets your requirements. We found it met ours and more, helping us gain confidence from our customers and solve a nagging problem in the performance of a third-party application.

We are just customers and end-users.

I'd rate the solution at an eight out of ten. We're pretty happy with its capabilities in general.

I'd recommend the solution to other users and organizations.

I would say use it, but people also have to know that they have to do their own due diligence and they have to make sure that their servers are okay. My advice would be to gather statistics on the servers as the tests are running, so that if the test indicates that there's something wrong, you can quickly look to the CPU, to the memory, to get an idea if it looks like it's an internal issue, or if it looks like it's an external issue.

I would rate this solution an eight out of ten.

I would rate it a seven out of ten. I would recommend it. 

I would like for it to be Windo-based. It should have the ability to be implemented into Windows applications. 

Excellent product!

Having a simple setup and being able to get the tests up and running right away, is the key for this solution.

When selecting a vendor, I look at ease of use, support, product maturity, and their partner model.

BlazeMeter is a great solution to run your existing tests. You will need detailed knowledge of JMeter to get the most out of your testing and BlazeMeter offer comprehensive training if you are new to this.

Look for your needs. This product is not a complete load-testing solution. It does offer certain types of load testing like URL testing but, other than that, we did not find them useful.