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, IDERA, Microsoft and others in Test Management Tools."The most valuable feature is the RFT because it allows us to automate manual test cases."
"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."
"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."
"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 one feature that has not allowed us to switch to any other solution is the integration with functional testing."
"It's very reliable as a solution."
"It's basically the way to show the work that we do as QA testers, and to have a historical view of those executions."
"As a system administrator, HPE ALM can be flexibly configured so that it can accommodate a variety of defined project lifecycles and test methodologies."
"The execution module and the test planning module are definitely the most valuable features. The rest we use for traceability, but those are the two modules that I cannot live without."
"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 product can scale."
"The solution's support team was always there to help."
"Quality management, project management from a QA perspective - testing, defect management, how testing relates back to requirements."
"I personally found the defect tracking feature very useful in my ongoing project."
"Works well for test management and is a good testing repository."
"UI and UX are pretty easy to understand without much of a problem."
"Being able to log into Defects, go right into JIRA, add that defect to the user story, right there at that point, means we connect all of that. That is functionality we haven't had in the past. As a communication hub, it works really well. It's pretty much a closed loop; it's all contained right there. There's no delay. You're getting from the defect to the system to JIRA to the developer."
"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 integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"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."
"I found the reporting aspect to be the most valuable as it provided a comprehensive overview of the efforts needed and the workload for individual tests."
"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."
"It would be helpful if we could assign a hierarchy to a group of test cases."
"I think it's fine from a performance perspective but usability is something that needs improvement."
"RQM could be improved by adding a feature that allows test requirements to be selected when creating a task plan."
"While RQM allows for running tests and viewing results, it could be further enhanced in terms of performance and speed."
"Mainly Quality Assurance and DevOps, but of course the whole company and management areas with more knowledge of quality and client success approach."
"Currently, the user interface needs to be more user-friendly."
"Organizing the test cases is tedious. There is no mechanism to keep and maintain the test cases as hierarchy. This should be seriously addressed."
"Integration capabilities with other vendors' tools should improve."
"Sometimes I do run my queries from the admin login. However, if I want to reassess all my test cases, then I am still doing this in a manual manner. I write SQL queries, then fire them off. Therefore, a library of those SQL queries would help. If we could have a typical SQL query to change the parameters within test cases, then this is one aspect I can still think that could be included in ALM. Though they would need to be analyzed and used in a very knowledgeable way."
"Quality Center's ability to connect all the different projects to reflect status and progress is quite complicated. We may develop something because there are so many projects. Right now, I have to do something which Quality Center is really not designed for: over reporting. This is a very big problem right now. We may develop some controls, but it is problem at the moment. I love Quality Center for individual projects to work with it. However, if you have a lot of projects for Quality Manager to do cross reporting on many projects, then it's almost impossible. It takes a lot of time."
"It is not a scalable solution."
"ALM Quality Center could be improved with more techniques to manage Agile processes."
"The support is not good and the documentation is not consistent."
"I would rate it a 10 if it had the template functionality on the web side, had better interfaces between other applications, so that we didn't have dual data entry or have to set up our own migrations."
"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."
"An area for improvement in Micro Focus ALM Quality Center is not being able to update the Excel sheet where I wrote the test cases. Whenever I update some test cases, I'm unsuccessful because there is overlapping data or missing cases from the sheet."
"The support for Tricentis qTest has room for improvement. The response could be better."
"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."
"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."
"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."
"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."
More OpenText ALM / Quality Center Pricing and Cost Advice →
