We performed a comparison between IBM Rational Quality Manager, Tricentis qTest, and Tricentis Tosca based on real PeerSpot user reviews.
Find out what your peers are saying about OpenText, Microsoft, IDERA and others in Test Management Tools."RQM is something that we use everyday, so it has to be up and running, otherwise we would lose everything."
"Reusability and integration capabilities which make it a great choice for organizations that use a variety of development tools and platforms."
"The most valuable feature is the RFT because it allows us to automate manual test cases."
"Latest features include versioning of testings which can be great when used for multiple releases of a product."
"RQM's best features are integration with test automation and performance testing."
"It allows user to add whichever widget (predefined) based on the need. It has integration with CCM and RM to achieve traceability."
"It's very reliable as a solution."
"Integration with the other professional tools is a very strong advantage, so that we can have a traceability between the requirements and defects in Rational Team Concert. That's the most important aspect."
"UI and UX are pretty easy to understand without much of a problem."
"The main thing that really stuck out when we started using this tool, is the linkability of qTest to JIRA, and the traceability of tying JIRA requirement and defects directly with qTest. So when you're executing test cases, if you go to fail it, it automatically links and opens up a JIRA window. You're able to actually write up a ticket and it automatically ties it to the test case itself."
"The solution's real-time integration with JIRA is seamless."
"What I found most valuable in Tricentis qTest is that it doesn't require installation. You use it through the URL. It also has an excellent reporting feature."
"Works well for test management and is a good testing repository."
"The JIRA integration is really important to us because it allows our business analysts to see test results inside the JIRA ticket and that we have met the definition of "done," and have made sure we tested to the requirements of the story."
"The test automation tracking is valuable because our automated testing systems are distributed and they did not necessarily have a single point where they would come together and be reported. Having all of them report back to qTest, and having one central place where all of my test executions are tracked and reported on, is incredibly valuable because it saves time."
"The most valuable feature is reusing test cases. We can put in a set of test cases for an application and, every time we deploy it, we are able to rerun those tests very easily. It saves us time and improves quality as well."
"The most valuable feature of Tricentis Tosca is the Tosca Commander. Functionality is another thing I find most valuable in the solution."
"We are satisfied with the support of Tricentis."
"It's a simple tool, particularly in terms of system testing. You can also convert and automate using Tricentis Tosca with ease."
"The technical support is good, we were satisfied."
"We can also create customized functions. For example, if something isn't supported in Tricentis Tosca Commander, we can create our own function to integrate it with Tosca Commander, so we can utilize it and integrate with the macros."
"The low code is the best feature."
"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."
"The feature that I have found the most valuable is the recovery and cleanup process. Suppose there is a list of test cases and one test case has failed, it should not impact the other test cases. We can reuse the same test case. We can change the configuration of parameters and then use the test cases on the same thing. So, that's a useful thing. Otherwise, we have to use the cleanup process. Another useful feature is to have our own library files. We can create our objects in the libraries and reuse them. There is no need to create duplicate data for that. They have been giving some enhancements recently which means integration is also there. They've integrated with different software like Jenkins, Bamboo. So, we can also create pipeline points. They have recently given SAP and everything, which is very useful."
"Organizing the test cases is tedious. There is no mechanism to keep and maintain the test cases as hierarchy. This should be seriously addressed."
"While RQM allows for running tests and viewing results, it could be further enhanced in terms of performance and speed."
"Integration capabilities with other vendors' tools should improve."
"Mainly Quality Assurance and DevOps, but of course the whole company and management areas with more knowledge of quality and client success approach."
"I think it's fine from a performance perspective but usability is something that needs improvement."
"It would be helpful if we could assign a hierarchy to a group of test cases."
"Currently, the user interface needs to be more user-friendly."
"Adding support for uploading a collection of test cases would be a helpful addition."
"As an admin, I'm unable to delete users. I'm only able to make a user inactive. This is a scenario about which I've already made a suggestion to qTest. When people leave the company, I should be able to delete them from qTest. I shouldn't have to have so many users."
"The support for Tricentis qTest has room for improvement. The response could be better."
"We feel the integration between JIRA and qTest could be done even better. It's not as user-friendly as qTest's other features. The JIRA integration with qTest needs to mature a lot... We need smarter execution with JIRA in the case of failures, so that the way we pull out the issues again for the next round is easy... Locating JIRA defects corresponding to a trait from the test results is something of a challenge."
"You can add what I believe are called suites and modules. I opened a ticket on this as to what's the difference. And it seems there's very little difference. In some places, the documentation says there's no difference. You just use them to organize how you want. But they're not quite the same because there are some options you can do under one and not the other. That gets confusing. But since they are very close to the same, people use them differently and that creates a lack of consistency."
"I would really love to find a way to get the results, into qTest Manager, of Jenkins' executing my Selenium scripts, so that when I look at everything I can look at the whole rather than the parts. Right now, I can only see what happens manually. Automation-wise, we track it in bulk, as opposed to the discrete test cases that are performed. So that connection point would be really interesting for me."
"I really can't stand the Defects module. It's not easy to use. ALM's... Defects Module is really robust. You can actually walk through each defect by just clicking an arrow... But with the qTest Defects module you can't do that. You have to run a query. You're pretty much just querying a database. It's not really a module, or at least a robust module. Everything is very manual."
"The Insights reporting engine has a good test-metrics tracking dashboard. The overall intent is good... But the execution is a little bit limited... the results are not consistent. The basic premise and functionality work fine... It is a little clunky with some of the advanced metrics. Some of the colorings are a little unique."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"Many times when we have raised a ticket, we did not get an urgent response."
"There should be ease of data manipulation within automation test cases."
"The solution should work with the Linux platform. Right now, it only runs on Windows."
"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."
"The Test Management options are still weak - improvement is outlined, but not yet visible. I"
"First, Tricentis could improve Tosca's Linux scripting. We can automate Linux scripting, but there are a few commands that Tosca doesn't support. DVS support and the object identification mechanism could also be better."
"You need to spend much more time learning the tool and how to use it, compared to others."
"In Tosca, I see that there are no user guides."
