We performed a comparison between Apache JMeter and Tricentis Tosca based on real PeerSpot user reviews.
Find out in this report how the two API Testing Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It's very easy to install, and it's very easy to code and develop the script."
"We really appreciate that the solution comes with a live community, which continuously provided plugins and support protocols."
"It is very quick and user-friendly."
"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 metrics part of it and the ability to write your custom code to do some specific tests in the performance testing space are the most valuable features."
"The recording and playback functionality is helpful."
"It's stable and reliable."
"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."
"We have multiple applications, and it supports parallel execution. It has mobile automation."
"It's stable and reliable."
"It's integrated with different technologies, desktop applications, package solutions like SAP, and mobile applications."
"The tool can be handled without any knowledge in parameterisation, especially the TestCaseDesign which makes the tool mighty and stable."
"Very user-friendly and the low code automation is really helpful."
"This tool has test data management capability along with test management."
"The use of automation is most valuable."
"Tricentis Tosca is a really cool tool that you don't have to be technical to use it. Additionally, the solution is easy to use. The modules, libraries, and reusable are in an efficient way to update all the tests. I find it spot on with that. We also started using the design which we switched from Excel. The design was superior to Excel."
"It will be much easier, and beneficial for the individual to run it on their own machines rather than having a high-end infrastructure, more CPUs, or more memory that has been consumed by Apache JMeter."
"The reporting section of the solution can be better."
"The only thing is the learning curve. It's high."
"The reports in Apache JMeter could improve."
"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."
"Self-healing and page rendering for the end-users are not available in Apache JMeter."
"It has some proxy-based dependencies which require specific proxies to be set up or disabled, which causes problems."
"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."
"Tricentis Tosca currently does not support any mobile testing and can be improved."
"Tricentis Tosca could improve on the ease of use. There is a steep learning curve. The reporting section could be better and some of the new features could be simplified. Additionally, the user management of the client and the server are confusing. There should not be two."
"The product needs to improve its pricing. It also needs to improve the infrastructure and DEX agent setup."
"It can be quite expensive."
"Might have a learning curve, as it does not follow the traditional Record-Play functionality, but tests have to be built from requirements or Agile story cards."
"They can make it more stable. I have used this tool for SAP applications. They have an alliance with SAP, and it mostly worked fine, but there were a few glitches. However, we got the required support from the Tricentis team. They are coming up with their new versions and upgrades with respect to how the Tricentis systems as cloud applications are updated, and it would be good if they have a robust accelerator pack."
"What needs to be improved in Tricentis Tosca is its centralized repository mechanism because it's not as flexible. The repository in the solution where you store the data and the script for test automation is quite an old-fashioned mechanism that could be improved."
"One thing to improve in Tricentis Tosca is that it's not compatible with Excel based forms. Another area for improvement is that the tool is not compatible with OpenText applications. The support and licensing cost for it also need improvement. The tool also needs cloud support, as it's currently on-premises only."
Apache JMeter is ranked 3rd in API Testing Tools with 82 reviews while Tricentis Tosca is ranked 2nd in API Testing Tools with 96 reviews. Apache JMeter is rated 7.8, while Tricentis Tosca is rated 8.2. 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 Tricentis Tosca writes "Does not require coding experience to use and comes with productivity and time-saving features ". Apache JMeter is most compared with BlazeMeter, Postman, Tricentis NeoLoad, OpenText LoadRunner Professional and SmartBear LoadNinja, whereas Tricentis Tosca is most compared with OpenText UFT One, Katalon Studio, Worksoft Certify, Postman and SmartBear TestComplete. See our Apache JMeter vs. Tricentis Tosca report.
See our list of best API Testing Tools vendors and best Regression Testing Tools vendors.
We monitor all API 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.