We performed a comparison between OpenText ALM / Quality Center and Tricentis qTest based on real PeerSpot user reviews.
Find out in this report how the two Test Management Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."I love to use this solution with single projects. It has helped our productivity. With the metrics that I receive, I can put them onto the management model so I can see them there. It has reduced our time for project management and controls by 20 percent."
"The most valuable user feature that we use right now is the camera."
"It has a good response time."
"It's user friendly, scalable, and very stable and strong. It's cooperative, meaning that I can assess the test to check it and follow the flow of defects, and the developers and the business can use this tool to follow the test process."
"The tools could be useful if we were utilizing them more effectively"
"I love linking/associating the requirements to a test case. That's where I get to know my requirement coverage, which helps a lot at a practical level. So, we use the traceability and visibility features a lot. This helps us to understand if there are any requirements not linked to any test case, thus not getting tested at all. That missing link is always very visible, which helps us to create our requirement traceability matrix and maintain it in a dynamic way. Even with changing requirements, we can keep on changing or updating the tool."
"We are able to use Micro Focus ALM Quality Center for test management, defect management, test process, test governance activities, and requirement management. We are able to achieve all of this, the solution is very useful."
"The integration with UFT is nice."
"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."
"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 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."
"Works well for test management and is a good testing repository."
"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..."
"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."
"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."
"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."
"If they could improve their BPT business components that would be good"
"When it came to JIRA and Agile adoption, that was not really easy to do with ALM. I tried, but I was not able to do much on that... There is room for improvement in the way it connects to and handles Agile projects."
"ALM only works on Internet Explorer. It doesn't work on any other browser. In my opinion, Internet Explorer is generally a bit slower. I would like to see it work on Chrome or on other browsers."
"Defect ageing reports need to be included as built-in."
"There's room for improvement in the requirements traceability with Micro Focus ALM Quality Center. That could use an uplift."
"The version of Micro Focus ALM that we use only works through Internet Explorer (IE). We have to communicate to everyone that they can only use IE with the solution. This is a big limitation. We should be free to use any type of browser or operating system. We have customers and partners who are unable to log into the system and enter their defects because they work on a different operating system."
"The Agile methodology is now being used across all the organizations, but in this solution, we don't have a dashboard like Jira. In Jira, you can move your product backlogs from one space to another and see the progress, that is, whether a backlog is in the development stage or testing stage. Micro Focus ALM Quality Center does not have this feature. It is typically very straightforward. You just execute the test cases from it, and you just make them pass, fail, or whatever. They can also improve its integration with Jira. The browser support needs to be improved in this because it supports only Internet Explorer as of now. It does not have support for Firefox, Chrome, Safari, or any other browser. There are also some performance issues in it. Let's say that you are doing the testing, and you found something and are logging the defect. When you try to attach several or multiple screenshots with the defect, it slows down, which is a very common problem people face. I would like them to include a functionality where I am able to see the reports across all the projects. When you have multiple projects, being a manager, I would like to see the reports across all the projects. Currently, there is no single sign-on through which we can get all the information at one place. You need to log into it project-wise. If you have ten projects, you can't view the information in one dashboard."
"The performance could be faster."
"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."
"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."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"The support for Tricentis qTest has room for improvement. The response could be better."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"The installation of the software could be streamlined. We pay for the on-premise support and they help us a lot, but the installation is something which is very command-line oriented."
"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."
"Reporting shouldn't be so difficult. I shouldn't have to write so many queries to get the data I'm looking for, for a set of metrics about how many releases we had. I still have to break those spreadsheets out of there to get the data I need."
More OpenText ALM / Quality Center Pricing and Cost Advice →
OpenText ALM / Quality Center is ranked 1st in Test Management Tools with 197 reviews while Tricentis qTest is ranked 6th in Test Management Tools with 16 reviews. OpenText ALM / Quality Center is rated 8.0, while Tricentis qTest is rated 8.4. The top reviewer of OpenText ALM / Quality Center writes "Offers features for higher-end traceability and integration with different tools but lacks in scalability ". On the other hand, the top reviewer of Tricentis qTest writes "Puts all our test cases in one location where everyone can see them. qTest also allows the segregation of different types of Testing". OpenText ALM / Quality Center is most compared with Microsoft Azure DevOps, OpenText ALM Octane, Jira, Zephyr Enterprise and OpenText UFT One, whereas Tricentis qTest is most compared with Tricentis Tosca, TestRail, Zephyr Enterprise, TFS and Panaya Test Dynamix. See our OpenText ALM / Quality Center vs. Tricentis qTest report.
See our list of best Test Management Tools vendors.
We monitor all Test Management 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.
