BlazeMeter Continuous Testing Platform

Best thing about blazeMeter is to set testbed for Load, Stress and Functional testing testing. Setting up for batches of multiple test cases to execution on very less time that makes it user friendly. Integration with Jmeter and Jenkins helps to align testcases in pipeline.

- User-friendly interface, easy to understand and workflow is very simple. - Record & run test scripts with simple steps. - It can also import existing projects. - Reporting and graph features are very accurate - Just because of cloud services, I can reduce unnecessary cost and time.

The UI of the tool is excellent, and intuitive. Things are exactly where you expect them to be, and little time is spent trying to figure out where you are and where you need to go. Creating a mock service could not be easier. For first time users, the creation wizard essentially holds your hand for the entire process and does an excellent job explaining what you are doing. Once you're familiar, new mock services can be created in minutes. The longest part of the this whole process is planning. The support that the Blazemeter provides in unparalleled. They are quick in responding to tickets and eager to finding the best solution, truly a great team to work with.

It is cost effective for tight budget organisation. implementing BlazeMeter at large scale makes it very expensive for the organisation at frequent testing. Learning and Implementation of BlazeMeter with new tester make it some complicated. Some new users finds it complicated while Stress testing on product.

Billing should be more reasonable, it should be exhaustive time based not on the executed test based.

When working with transactions of mock services, some of the 3rd party tools that Blazemeter uses for parsing JSON or XML payloads can be a bit clunky. There are a lot of times where I am pasting over payloads and there are strange formatting errors when I'm pulling my payloads directly from a live service. I definitely think there are better solutions out there. The process of parameterizing fields in transaction payloads is a bit difficult to do, and not explained all that well. Blazemeter does offer documentation for doing so, but I feel that it is lacking, and could be more robust. I think that there could be more tools for organizing mock services. When you land on the homepage of mock services you are greeting with a wall of mocks that are sorted in order of the time they are created. It's a bit messy. I think if there were a folder system for organizing mocks it would work a lot better. You do have the option to place mocks under a service name and then sort by that service to see only those mocks under that service, but what if I wanted to get more granular?