Jmeter vs neoload6/24/2023 ![]() That has improved recently, but it's still a problem with unusually large test cases. When reviewing finished cases, it sometimes takes a while for BlazeMeter to load. That means I have to wait for three to four minutes again." "The performance could be better. every time I rerun the same test, it is downloaded again. That's the bad part of the performance testing. It takes a minimum of three minutes or so to start the test itself. Let's say I'm performance testing with a high-end load configuration. ![]() This user only has access to mock services." That feature set doesn't currently exist." "One problem, while we are executing a test, is that it will take some time to download data. It would be nice if there was a more granular control where you could say, "This person can only do A, B, and C," or, "This user only has access to functional testing. Currently, BlazeMeter controls everything at a workspace level, so a user can view or modify anything inside that workspace depending on their role. I'd like to capture items via snapshots." "The seamless integration with mobiles could be improved." "BlazeMeter needs more granular access control. For example, there are only filter requests for a time of less than 5 seconds." "The should be some visibility into load testing. One feature that I missed was not having a time filter, which I had in ELK. "The Timeline Report panel has no customization options. Instead of updating a hundred different test cases, we update one action group, and the test cases using that action group will update." That also means we have a single point for maintenance when updates are required. ![]() They act like functions or methods and code, allowing us to reuse portions of our tests. It allows me to essentially give BlazeMeter multiple JMeter scripts and a YAML file, and it will orchestrate and execute that load test and all those scripts as I define them." "The feature that stands out the most is their action groups. It's like the tourist backend component of BlazeMeter. This feature has helped us a lot because we can reuse other vendors' performance scripts that they have used with JMeter before." "The orchestration feature is the most valuable. BlazeMeter sets us up for our traditional hosting platforms and application stack as well as the modern cloud-based or SaaS-based application technologies." "BlazeMeter can be used for both API and performance testing, it is a multi-facility tool." "One thing that we are doing a lot with the solution, and it's very good, is orchestrating a lot of JMeter agents. 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." "It's a great platform because it's a SaaS solution, but it also builds the on-premises hosting solutions, so we have implemented a hybrid approach. The cloud load generator is there when we need it and is the feature we leverage the most." "The stability is good." "With the help of the Mock Services, we are overcoming everything. "Using cloud-based load generators is highly valuable to us, as we can test from outside our network and increase load generation without having to upscale our hardware as much.
0 Comments
Leave a Reply. |