The on-the-fly test data improved our testing productivity a lot. The new test data features changed how we test the applications because there are different things we can do. We can use mock data or real data. We can also build data based on different formats. 

For example, an IMEI number should be a 15 digit number. If you need various combinations of it, BlazeMeter can do it as long as we can provide regular expressions and say, "The numbers should be in this format." Mobile subscriber identities, which are pretty common in the telecom world, are easy. This solution has changed how we test things. Fundamentally, it helped us a lot.

Previously, most of the test projects that I delivered before I moved into automation used to take months. Now, the entire API test is completed within minutes. Because we look at millisecond latency, the tests don't take any longer. It's less than a minute. 

The moment those tests run on schedule, I don't really need to do anything. I just concentrate on what other tests I can add and what other areas I can think of. 

Recently, I have seen BlazeMeter's other products in their roadmap, and they're really cool products. They use some AI and machine learning to build new API level tests. I don't think it's available to the wider market yet, but there are some really cool features they're developing.

BlazeMeter reduced our test operating costs by quite a lot because normally to do the same level of testing, we need loads of resources, which are expensive. Contractors and specialists are expensive, and offshore is quite expensive. However we do it, we have to spend a lot of time. Running those tests manually, managing the data manually, and updating the data manually take a lot of time and effort. With this project, we definitely save a lot in costs, and we give confidence to the stakeholders.

For previous projects and even smaller projects, we used to charge 100k to 200K for testing. We're using BlazeMeter for massive programs, and the cost is a lot less.

The range of test tools that BlazeMeter provides is amazing. There are more than 18 tools, which gives us freedom of choice.

It's very important to us that BlazeMeter is a cloud-based and open-source testing platform. It's critical for our organization because we are increasingly moving from on-premises application hosting to cloud-native hosting.

BlazeMeter has definitely improved the productivity of our organization, especially because of the integration features. Engineering productivity has improved because people are able to use the tool of their choice. This increases our delivery velocity.

From the operational-benefits perspective, we save infrastructure costs because we don't have to host this massive product on infrastructure. We also save operational costs. We don't need a big team because it's a SaaS platform.

BlazeMeter gives us a centralized place to execute load tests, do reporting, and have different levels of user access control. BlazeMeter has a full API, which is the feature that's given us a lot of value. It allows us to integrate with BlazeMeter in our CI/CD pipelines, or any other fashion, using their APIs. It helps increase our speed of testing, our reporting, and our reporting consistency, and gives us a central repository for all of our tests, execution artifacts, and results.

BlazeMeter added a mock services portion. We used to leverage a different product for mock services, and now that's all done within BlazeMeter. Mock services help us tremendously with testing efforts and being able to mock out vendor calls or other downstream API calls that might impact our load testing efforts. We can very easily mock them out within the same platform that hosts our load tests. That's been a huge time saver and a great value add.

BlazeMeter absolutely helps bridge Agile and CoE teams. It gives us both options. BlazeMeter is designed so that we can grant access to whoever needs it. We can grant access to developers and anyone else on an Agile team. It allows us to shift left even farther than a traditional center of excellence approach would allow us.

It absolutely helps us implement shift-left testing. One of the biggest features of shifting left is BlazeMeter's full, open API. Regardless of the tools we're leveraging to build and deploy our applications, we can integrate them with BlazeMeter, whether that's Jenkins or some other pipeline technology. Because BlazeMeter has a full API, it lets us start tests, end tests, and edit tests. If we can name it, it can be done via the API. It tremendously helps us shift left, run tests on demand, and encode builds.

Overall, using BlazeMeter decreased our test cycle times, particularly because of the mock service availability and the ease with which we can stand out mock services, or in the case of an Agile approach, our development teams can stand out mock services to aid them in their testing. 

It's fast, and the ability to integrate with pipelines increases our velocity and allows us to test faster and get results back to the stakeholders even quicker than before.

The overall product is less costly than our past solutions, so we've absolutely saved money.

In load testing, BlazeMeter is utilized to create realistic user behavior. It's particularly friendly for web LoadRunner users, providing proper pacing and timing control. 

Moreover, it allows for comprehensive control over user behavior across scripts, such as ramp-up and steady-state phases, which is crucial for conducting incremental load tests and more. This level of control isn't as easily achievable with other tools, but with JMeter and BlazeMeter, it's possible.

Incremental load testing is a type of test you can perform with JMeter. It's a technique that isn't straightforward without BlazeMeter. BlazeMeter facilitates this process.

Before BlazeMeter, we didn't have a performance test aggregator. They were running one-off JMeter tests that weren't stored in a repository. JMeter can generate some reporting, but it's nowhere near as nice as what BlazeMeter provides. And it's more readily understood by the development teams that we work with and the management. That part is great.

We initially purchased the tool for performance testing, but we discovered that we had access to functional testing, so we started using that. That's been great for a lot of the same reasons. It increases visibility and gets everybody on the same page about which tests can run and the status of our regression and functional tests.

BlazeMeter can create test data for performance and functional testing. We don't have much use for that currently, but I could see that being useful for individual functional tests in the future. It's nice to have automatic data generation for test cases.

We haven't used BlazeMeter for shift-left testing. The functional testers embedded with the sprint teams don't do automation. That's all kicked down the road, and the automation is done outside of the sprint. While there is a desire to start attacking things that way, it never really got any traction.

I believe BlazeMeter has also reduced our test times, but I can't quantify that.
It's helped us with our test data challenges. I think they have a lot of great implementation, so I don't want to detract from that, but we have some problems with our applications and some custom things. I think we work on a different platform than many other people do, so it hasn't been as beneficial to us probably as it would be for many other people.

Basically, my company wanted to use BlazeMeter to act as a trigger for around 1,05,000 users who communicate with each other. For the aforementioned aspect, the first option was to choose between NeoLoad and LoadRunner, while the second option was to choose BlazeMeter, which runs on the cloud. With Blazemeter, it was easy for my company to create a script and then trigger it.

BlazeMeter opened up performance testing for us. Our old solution was a client-based performance testing tool, and for staff to access it, they needed to remotely connect to a Windows VM and book time with that controller. Now our tool is web-based, and we onboarded 12 to 14 teams to BlazeMeter, which would not have happened before. Our CoE team was the go-to for performance testing, but the solution has opened up the practice to the whole enterprise, making teams more self-sufficient, and that's the most significant benefit. Performance testing is no longer segregated to one team.

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.

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

WIP.

Building an in-house group of load generation JMeter servers to load test usually takes time and effort. BlazeMeter makes all that simple.

For us in particular, we're a product that gets heavily used during the election season. We've always had trouble handling this burst in the past, so this past year, I've started using BlazeMeter at this company. We took from January to July using BlazeMeter to really model out what the traffic looked like in previous years and to be able to handle the load when November came and it went through just fine without a glitch.

By using this tool, a performance engineer was able to identify performance bottlenecks, and after fixes was applied, overall product quality improved.

We no longer have to guess whether deploying new code will affect performance or not. This ensures we are ready to meet customer demand, even at peak traffic times.

Provided an easy to use tool to measure the performance of our most critical business application, along with the expertise of BlazeMeter to properly generate the test case.

It has allowed us to test the impact of vendor updates to their software on the performance of the web component, which we are now doing as updates get released (6 month release cycle, so only one retest thus far).

System Administrators are performing the testing, as the software isn't ours and we don't presently develop our own software this was a new need and we don't have anything to compare to other than anecdotal evidence from users. We were able to compare results post-testing by comparing Google Analytics data and found that the improvements we put into place as result of the testing did have positive effect on both pageload and generation timings along with improving the overall conversion rate for the tool as well.

It has helped us simulate heavy load situations so we can fix performance issues ahead of time. This ensures that we are ready for real customer load.

One example of what happened is that we noticed that there was a significant difference between our two sites. It turned out that there was a configuration on the network side so after we fixed that, the performance was much better.

It helped to identify where there were problems, and then we could go investigate and figure out what was going on. We didn't just do one test, but this was a one-time sanity check on the new environment. One time lasted three months, but during that time, I would say we did it once a week.

Using this product has improved the way our organization does testing.

BlazeMeter has allowed us to simplify and speed up our load testing process. Before BlazeMeter, we used to set up an ad-hoc infrastructure with no formal structure in terms of the scope, or how and when to provision it. This meant additional costs in terms of resources and time for managing the load-test infrastructure.

BlazeMeter has allowed my organization to identify bottlenecks in our infrastructure and better prepare for large amounts of traffic.

It has allowed us to run performance tests in order to help determine if we can scale well.

BlazeMeter allows us to easily run our existing load testing solutions at massive scale.

All of our consultants can use BlazeMeter. Traditionally our tests were run in JMeter and this was limited to technical users. BlazeMeter allows the use of the same tests but in a more user-friendly environment where all of our consultants can run the tests and access the results.

BlazeMeter is a cost effective way to scale our existing JMeter load tests.

We were planning to load test this product for a significant release. It was somewhat helpful.