We performed a comparison between IBM Rational Quality Manager, OpenText ALM / Quality Center, and Tricentis qTest based on real PeerSpot user reviews.
Find out what your peers are saying about OpenText, Microsoft, IDERA and others in Test Management Tools.
"RQM's best features are integration with test automation and performance testing."
"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."
"It allows user to add whichever widget (predefined) based on the need. It has integration with CCM and RM to achieve traceability."
"RQM is something that we use everyday, so it has to be up and running, otherwise we would lose everything."
"Latest features include versioning of testings which can be great when used for multiple releases of a product."
"It's very reliable as a solution."
"The most valuable feature is the RFT because it allows us to automate manual test cases."
"The one feature that has not allowed us to switch to any other solution is the integration with functional testing."
"You can maintain your test cases and requirements. You can also log the defects in it and make the traceability metrics out of it. There are all sorts of things you can do in this. It is not that complex to use. In terms of user experience, it is very simple to adopt. It is a good product."
"Most of the features that I like the best are more on the analytics side."
"The test-case repository and linkage through to regression requirements will absolutely be a key component for us. We haven't got it yet, but when we've got an enterprise regression suite, that will be a key deliverable for them. We will be able to have all of the regression suite in one place, linked to the right requirements."
"The integration with UFT is nice."
"As a stand-alone test management tool, it's a good tool."
"You can do your development from start to finish: starting with the requirements, ending with defects, and testing in-between."
"The AI and functionality interface are useful."
"Integration with other HPE products."
"I like the way it structures a project... We're able to put the test cases into qTest or modify something that's already there, so it's a reusable-type of environment. It is very important that we can do that and change our test data as needed..."
"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 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 most important feature which I like in qTest manager is the user-friendliness, especially the tabs. Since I'm the admin, I use the configuration field settings and allocate the use cases to the different QA people. It is not difficult, as a QA person, for me to understand what is happening behind the scenes."
"The integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"The solution's real-time integration with JIRA is seamless."
"qTest helps us compile issues and have one place to look for them. We're not chasing down emails and other sources. So in the grand scheme of things, it does help to resolve issues faster because everyone is working off of the same information in one location."
"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."
"Integration capabilities with other vendors' tools should improve."
"Adding support for uploading a collection of test cases would be a helpful addition."
"Mainly Quality Assurance and DevOps, but of course the whole company and management areas with more knowledge of quality and client success approach."
"RQM could be improved by adding a feature that allows test requirements to be selected when creating a task plan."
"Currently, the user interface needs to be more user-friendly."
"I think it's fine from a performance perspective but usability is something that needs improvement."
"Organizing the test cases is tedious. There is no mechanism to keep and maintain the test cases as hierarchy. This should be seriously addressed."
"It would be helpful if we could assign a hierarchy to a group of test cases."
"If the solution could create a lighter, more flexible tool with more adaptability to new methodologies such as agile, it would be great."
"As soon as it's available on-premises we want to move to ALM Octane as it's mainly web based, has the capability to work with major tests, and integrates with Jenkins for continuous integration."
"Browser support needs improvement. Currently, it can only run on IE, Internet Explorer. It doesn't work on Firefox, doesn't work on Chrome, doesn't work on a Mac book. Those are the new technologies where most companies move towards. That's been outstanding for quite a while before it even became Micro Focus tools when it was still HP. Even before HP, that's always been an issue."
"The integration could be improved because with Agile technology you are working more quickly than with a top-down methodology."
"There are always new features and more support for new and legacy technology architectures with each release. But the bad news is a growing list of long-standing issues with the product rarely gets addressed."
"Micro Focus is an expensive tool."
"ALM Quality Center could be improved with more techniques to manage Agile processes."
"If they could improve their BPT business components that would be good"
"qTest offers a baseline feature where you can only base sort-order for a specific story or requirement on two fields. However, our company has so many criteria and has so many verticals that this baseline feature is not sufficient. We would want another field to be available in the sort order."
"I wouldn't say a lot of good things about Insights, but that's primarily because, with so many test cases, it is incredibly slow for us. We generally don't use it because of that."
"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."
"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."
"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."
"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."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"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."
More OpenText ALM / Quality Center Pricing and Cost Advice →
