"The test repository to follow the test progress is most valuable because we can easily create and manage a huge number of test scripts. We can copy and paste, replicate, and drag and drop many tests scripts. We can create test scripts en masse. When you have a high volume of tests, the tool is quite useful. It works well when you want to manage a lot of tests, such as you have 1,000 or more test scripts."
"It's integrated with different technologies, desktop applications, package solutions like SAP, and mobile applications."
"The mainframe testing and UI automation are the most valuable aspects of the solution."
"The most valuable feature of Tricentis Tosca is the Tosca Commander. Functionality is another thing I find most valuable in the solution."
"You can quickly build automated testing, manage it, and have it run on a regular basis to ensure that there are no issues."
"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."
"The use of automation is most valuable."
"This solution is very easy to learn and any non-programmer or manual tester, with little experience in automation, can pick it up quite easily."
"The automation engine is very strong, and it is very competitive in the market in terms of features. They develop a lot of features."
"The setup of Panaya Recorder is a bit complex. Panaya is a SaaS application, but you need to install some components on your computer. You need to set up your computer to allow Panaya Recorder to work. There are five or six things to do each time you install Panaya for any user. If you miss something, Panaya Recorder doesn't work. So, it is complex to install."
"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."
"Their license management should be improved. One of our customers is a global customer. They want to use one licensed server and then split the licenses based on the different users of the different business units, but currently, there is only one license server that everybody can access. There is no control, and that's why sometimes congestion can happen."
"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 have found that some of the functions could be missed in the solution for new users. They are not obviously present."
"The user management could improve in Tricentis Tosca because it is confusing. It would be better to have it in one place. Having to add it to the cloud and to a specific project can be a mess."
"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."
"Many times when we have raised a ticket, we did not get an urgent response."
"The UI does not have the option of automating the scroll bars."
Panaya Test Dynamix is ranked 12th in Regression Testing Tools with 1 review while Tricentis Tosca is ranked 1st in Regression Testing Tools with 26 reviews. Panaya Test Dynamix is rated 8.0, while Tricentis Tosca is rated 8.2. The top reviewer of Panaya Test Dynamix writes "Easy and very flexible usage. Provides a good picture of your progress and useful for a huge number of test scripts. Licensing model and the Panaya recorder installation can be improved". On the other hand, the top reviewer of Tricentis Tosca writes "Efficient operations, continuous improvements, and robust features". Panaya Test Dynamix is most compared with Micro Focus UFT One, Micro Focus ALM Quality Center, Worksoft Certify and Selenium HQ, whereas Tricentis Tosca is most compared with Micro Focus UFT One, Worksoft Certify, Katalon Studio, SmartBear TestComplete and Selenium HQ.
See our list of best Regression Testing Tools vendors and best Functional Testing Tools vendors.
We monitor all Regression 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.
@Jesús Antonio Santos Giraldo; both companies deliver excellent tools & services. It's going to come down to your use cases.
If you choose the wrong tool for your use case the risks are: Loss of time, money and opportunities. That's not going to be the tool's fault.
Tips that may help you in deciding:
- Use your current tools / last tools as benchmark to determine your future needs.
- Ask questions, here are a few to get you started:
-- What are your requirements?
-- Pros and cons of our current tools.
-- How much time do you want to spend developing and maintaining test scripts (assuming you want to automate)
--Who will work with the tool?
-- What do they have to say about their experience with current / past tools?
- Build a matrix based on feedback received, decide which points really matter in your matrix.
- Inform your org of the research you've done and ask for more input
- Go with a few key folks who work with / worked with the tools you are targeting and have a meeting with Tricentis / Panaya.
- Tell your story and ask how their tool can meet your need.
- Go back to your leadership and share what you learned,
- See if you can get a trial from the toolmakers. ;-) and try out a real world test.
- Make a documented decision on why tool X and not tool Y
Links to the companies you mentioned:
https://www.tricentis.com/sap/
https://www.panaya.com/sap/sap...
Hope this helps
John