We performed a comparison between Parasoft SOAtest, SonarQube, and Tricentis Tosca based on real PeerSpot user reviews.
Find out what your peers are saying about Tricentis, OpenText, Perforce and others in Functional Testing Tools."Technical support is helpful."
"Parasoft SOAtest has improved the quality of our automated web services, which can be easily implemented through service chaining and service virtualization."
"Since the solution has both command line and automation options, it generates good reports."
"We have seen a return on investment."
"The solution is scalable."
"Every imaginable source in the entire world of information technology can be accessed and used."
"If you want something that’s not provided out of the box, then you can write it yourself and integrate it with SOAtest."
"The testing time is shortened because we generate test data automatically with SOAtest."
"It is a very good tool for analysis despite its limitations."
"I like that it helps us maintain our work quality and code security."
"It has very good scalability and stability."
"We can create a Quality Gate in order to fail Jenkins jobs where the code coverage is lower than the set percentage."
"It assists during the development with SonarLint and helps the developer to change his approach or rather improve his coding pattern or style. That's one advantage I've seen. Another advantage is that we can customize the rules."
"It easily ties into our continuous integration pipeline."
"The most valuable feature is the security hotspot feature that identifies where your code is prone to have security issues."
"The most valuable features are that it is user-friendly, easy to access, and they provide good training files."
"The Model-Based Test Automation is the most valuable feature, where you can create reusable components. Even though we are using a scriptless automation tool, there still needs to be an understanding of how to create reusable components and how to keep refactoring and how to keep regression, the test scripts, at an okay level. We are coupling Tosca with some other risk-based testing tools, as well, but automation is primarily what we're using Tosca for, the scriptless, model-based technology which is driving automation for us."
"You can quickly build automated testing, manage it, and have it run on a regular basis to ensure that there are no issues."
"It is easy to maintain and easy to automate. No coding skills are required to automate. It is also easy in terms of transferring knowledge and skills. Many of my team members shifted over the past one and a half years, and there was no big issue with respect to knowledge sharing. It is a good tool that enables me to re-automate my scripts and update my scripts as quickly as possible. Looking at the amount of rework and maintenance activity that we had done for our scripts, it might have been a nightmare with some other scripting tool."
"Software testing tool that has multiple features. It's good to use for SAP testing, and it helps reduce test execution time."
"It's a simple tool, particularly in terms of system testing. You can also convert and automate using Tricentis Tosca with ease."
"The most valuable feature is being able to create a test case by recording some scenarios and then leasing that task case to other scenarios."
"Compared to other tools we have been looking at, you don't have to be a programmer to operate it, though it helps. It also a product that can be used by business people."
"As a codeless automation tool, the product offers a user-friendly experience without requiring extensive coding knowledge. Users can easily handle various applications, including web applications, SAP applications, Windows applications, and even Salesforce applications, without manual coding."
"Tuning the tool takes time because it gives quite a long list of warnings."
"Enabling/disabling an optional element of an XML request is only possible if a data source (e.g., Excel sheet) is connected to the test. Otherwise, the option is not available at all in the drop-down menu."
"Parasoft SOAtest has an internal refresh function where you can refresh the software to show the changes you’ve made in your projects. Unfortunately this function does not work properly, because it often does not show the changes after you’ve hit te refresh button a few times."
"UI testing should be more in-depth."
"The product is very slow to start up, and that is a bit of a problem, actually."
"Reports could be customized and more descriptive according to the user's or company's requirements."
"During the process of working with SOAtest and building test cases, the .TST files will grow. A negative side effect is that saving your changes takes more time."
"From an automation point of view, it should have better clarity and be more user friendly."
"There needs to be a shareable reporting piece or something we can click and generate easily."
"The time it took for me to do the whole process was approximately two hours because I had to download, read the documentation, and do the configurations."
"The solution could improve the management reports by making them easier to understand for the technical team that needs to review them."
"SonarQube could improve by adding automatic creation of tasks after scanning and more support for the Czech language."
"The interface could be a little better and should be enhanced."
"Having performance regression would be a helpful add on or ability to be able to do during the scan."
"I think the code security can be improved."
"From a reporting perspective, we sometimes have problems interpreting the vulnerability scan reports. For example, if it finds a possible threat, our analysts have to manually check the provided reports, and sometimes we have issues getting all the data needed to properly verify if it's accurate or not."
"In terms of areas for improvement, Tricentis has a variety of tools, even its test management tool called qTest. Tricentis Tosca does have integration with different Tricentis tools, but the integration is geared towards a larger organization perspective. For very small organizations that have minimal licenses, the integration needs to be improvised. For example, I belong to a smaller organization that has only one license, so the capability that the tool provides for integration isn't sufficient because my company needs to have separate workspaces. When Tricentis Tosca is going to be running, it is going to use that license, but my company wants another separate workspace to record, relay, and test. This is what my team has been struggling with, and the mechanism is probably there, but that needs more time and investigation, so I can't say that I'm one hundred percent certain that Tricentis Tosca, in terms of integration for a smaller organization is insufficient. Another area for improvement is that Tricentis Tosca is currently just a Windows-based tool which affects the market because nowadays, Windows isn't the only operating system, for example, there's also Apple or IOS that's moving much faster than Windows."
"I would like to see better integration with other testing tools."
"The main area where there is room for improvement is how they do upgrades. Going through this current upgrade, we were delayed a month because we are using a third-party tool. It's called Tosca Connect by Tasktop. When this latest upgrade broke that relationship between the two, it took Tricentis a month to come back with a workable solution... Their whole upgrade process needs to be better and cleaner, from an end-user standpoint."
"It requires some coding customization that requires expertise."
"Tricentis Tosca's performance could be better. Sometimes when we are remapping or when it is loading it can take a lot of time. There are free solutions that have better performance in this area."
"Tricentis Tosca currently does not support any mobile testing and can be improved."
"Setup wasn't that straightforward; it was more complex. It all depends on the environment, because there were a lot of errors on our applications. Therefore, it wasn't an easy setup for us."
"It would be of great help if they can fix the loading or performance issues. Sometimes, when I create the test case folder and test cases, it feels like it has loading or performance issues. When passing the objects, we can't sometimes find the exact element. We need to find out that exact location and just give the path for that, and then it works. In the pipeline, when creating Jenkins, we create the list execution for passing the execution list to the commander. I feel it is a bit late, by a fraction of seconds. I first thought it could be my mistake or a setting issue, but I worked on that, and it's not a mistake or a setting issue."
