"I like the fact that JMeter integrates well with other tools."
"The features that I appreciate are quite basic. It is easy to ramp up the threads and start calling the application. A lot of connectors can already be found within Apache JMeter, but we are not using the entire set because the integration between the customers and platform is based on HTTP. We are just going to produce lots of HTTP sequences."
"The scripting ability is most valuable. It is easy to use. There is a UI, and you can go in there and figure those things out. After you've got a good set of tests, you basically have a scripted document that you can grab and execute in a pipeline. It is pretty quick to set up, and you can scale it and version control it."
"The reports and analysis tools are very good. They are the solution's most valuable features."
"A lot of things are valuable. It is free. It has a lot of features, such as report generation and integration with CI/CD, which makes it very competitive with the other paid solutions available in the market. It is a good solution."
"The biggest thing I liked about it is that there is a huge user base out there, and being shareware and being Apache, if I have any question on how to get something done, I get 18 different answers. Out of those, there would be at least a few good approaches for what I was trying to do. So, the support system out there is most valuable."
"User-friendly and open source."
"The recording and playback functionality is helpful."
"The ability to quickly make your own components has been valuable."
"I was satisfied with the support given by customer service."
"The stability has always been very good."
"Performance-wise, it is a great tool."
"Easy to use and easily scalable."
"It is a very common and strong product. A lot of support is available for this product."
"It is very easy to use. You can handle a lot of things together at once in one package, which is a good point for us."
"The most valuable features are tools like IntelliSense and ReSharper."
"The plug-ins make the reports heavy and they have to be run in non-GUI mode."
"Currently, the integration pipeline is implemented by using Jenkins or a similar tool platform. These are continuous integration tools. As far as I know, integration is done by using custom scripts. It would be good if the integration with a continuous integration pipeline, like Jenkins or Hudson, can be done out of the box without using a script."
"I sometimes found the documentation to be not as explanatory as I would've liked it. In the cases that I can think of, I was looking for a rather hand-holding approach with Step A, B, and C, but then I realized that with a product that is open source like this, you can't do handholding. That is because there are so many different uses and different unique environments and setups for it, but I remember thinking a few times that if they only just said this."
"Automation is difficult in JMeter."
"JMeter output reports can be difficult to understand without training."
"You really need a technical team in order to really utilize the product."
"Because so much is being done these days with authentication processes, a better system for either getting bearer tokens or some kind of token-based authentication prior to executing APIs would benefit the product. It is there, and you can do things. It is just not real clean at this point. There should be a better authentication process for JMeter or some automation or better guidelines for gaining and utilizing tokens on the fly."
"We're like the solution to be more user-friendly."
"The pricing of this solution should be lowered."
"There are too many features with the product and I would like there to be less."
"The integration with Git needs improving because it is a bit disjointed and unpredictable."
"It needs more integration with other tools for monitoring. Microsoft also needs to make it more modern to make it work with microservices and the cloud. It is a bit outdated currently."
"In Visual Studio we still don't have anything which can pinpoint memory leaks on a certain code line."
"The solution is quite expensive."
"One of the problems with this solution is you need to be highly technically skilled to operate it, it is not for everyone."
Apache JMeter may be used to test performance both on static and dynamic resources, Web dynamic applications. It can be used to simulate a heavy load on a server, group of servers, network or object to test its strength or to analyze overall performance under different load types.
Apache JMeter is ranked 1st in Performance Testing Tools with 16 reviews while Visual Studio Test Professional is ranked 12th in Functional Testing Tools with 8 reviews. Apache JMeter is rated 7.6, while Visual Studio Test Professional is rated 8.2. The top reviewer of Apache JMeter writes "Easy to learn, and free to use but could be more user-friendly". On the other hand, the top reviewer of Visual Studio Test Professional writes "Offers lots of features, including memory analysis and code sharing". Apache JMeter is most compared with Postman, BlazeMeter, Micro Focus LoadRunner Professional, ReadyAPI and Cavisson NetStorm, whereas Visual Studio Test Professional is most compared with TFS, Katalon Studio, Tricentis Tosca, HCL AppScan and Micro Focus UFT Developer.
We monitor all Performance Testing Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.