We performed a comparison between Apache JMeter and Visual Studio Test Professional based on real PeerSpot user reviews.
Find out what your peers are saying about Apache, OpenText, Tricentis and others in Performance Testing Tools."JMeter is easy to use for a user who doesn't have too much knowledge of programming or certain languages."
"API testing, Database Testing, and MQ testing can be done with ease."
"We find the load testing feature valuable."
"Apache JMeter is well-known and widely used among developers, particularly on popular developer forums. While it may not have the most user-friendly interface, it offers strong support through official manuals and various articles from companies providing load testing services. The tool is free, has a substantial community, and serves as a fundamental choice for testers, especially those new to performance testing. While other tools like K6 may be more developer-oriented, JMeter's affordability and accessibility make it suitable for those without extensive performance testing experience."
"I like the fact that JMeter integrates well with other tools."
"The most valuable feature of Apache JMeter is its popularity. It is the best open-source tool with all the features needed."
"I appreciate JMeter's simplicity and power for performance testing."
"It is open source as well as relatively extendable. It allows us to extend and add additional functionality and features. Its deployment is also very easy."
"Customization is the most powerful feature of this product."
"Visual Studio Test Professional's most valuable feature is the rich IDE for doing code and test development."
"Visual Studio Test Professional is a very scalable solution."
"The whole suite is made for .NET development."
"Easy to use and easily scalable."
"One of the best documentation in the world."
"The user interface is very friendly."
"The most valuable feature is the in-built support for C# and .NET projects."
"The solution needs to improve reporting. Currently, there is not enough automation involved with the feature. For example, there should be an automatic way of saving reports."
"We would like some reporting and analysis tools to be added to this solution."
"The plug-ins make the reports heavy and they have to be run in non-GUI mode."
"It has some proxy-based dependencies which require specific proxies to be set up or disabled, which causes problems."
"JMeter's reporting is extremely rudimentary. The fundamental reporting mechanisms need to be drastically improved. It doesn't utilize an automatic session management mechanism or methods other tools use like parsing cookies and variables. Everything needs to be done manually. There's no automation."
"What needs improvement in Apache JMeter is the very high load requirements when you want to scale it beyond certain thresholds. For example, small to mid-range testing is very easily done with Apache JMeter, but if you scale and increase the load, then it would be a problem because the tool consumes a lot of resources, probably because Apache JMeter provides an enriched UI experience, so it consumes a lot of memory and requires high CPU usage. This means you have to manage your infrastructure, or else you'll have high overhead expenses. As Apache JMeter is a heavyweight tool, that is an area for improvement, though I'm unsure if Apache can do something about it because it could be a result of the way it's architected. What I'd like to see from Apache JMeter in the future is for it to transition to the cloud, as a lot of cloud technologies emerge around the globe, and a lot of people prefer cloud-based solutions or cloud-native tools. Even if a company has a legacy system, it's still possible to transition to the cloud. I've worked with a company that was an on-premise company that moved to the cloud and became cloud-native. If Apache JMeter could transition to the cloud, similar to k6, then it could help lessen the intense resource consumption that's currently happening in Apache JMeter."
"Until now, JMeter is not supporting most of the protocols."
"The UI has room for improvement."
"The solution can improve the startup time."
"The price could be improved."
"Visual Studio Test Professional could improve by having better integration with external databases."
"The performance could be faster."
"Sometimes, the solution hangs, so its performance could be improved."
"Visual Studio Test Professional is a little pricey."
"The documents on the Microsoft website are not very useful, and they ought to make it easier to find answers."
"One of the problems with this solution is you need to be highly technically skilled to operate it, it is not for everyone."
More Visual Studio Test Professional Pricing and Cost Advice →
Apache JMeter is ranked 1st in Performance Testing Tools with 82 reviews while Visual Studio Test Professional is ranked 7th in Functional Testing Tools with 48 reviews. Apache JMeter is rated 7.8, while Visual Studio Test Professional is rated 8.6. The top reviewer of Apache JMeter writes "It's a free tool with a vast knowledge base, but the reporting is lackluster, and it has a steep learning curve". On the other hand, the top reviewer of Visual Studio Test Professional writes "Customization is a key feature as is the ability to integrate with third-party services ". Apache JMeter is most compared with BlazeMeter, Postman, Tricentis NeoLoad, Katalon Studio and Akamai CloudTest, whereas Visual Studio Test Professional is most compared with TFS, Tricentis NeoLoad, SmartBear TestComplete, TestRail and Tricentis Tosca.
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.
