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."The tools could be useful if we were utilizing them more effectively"
"ALM Quality Center is a reliable, consolidated product."
"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 most valuable user feature that we use right now is the camera."
"I like that it integrates with the Jira solutions."
"Templates: Allows us to standardize fields, workflows throughout hundreds of HPE ALM projects."
"Ability to customize modules, particularly Defect Tracking module on company specific needs"
"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."
"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 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."
"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."
"Works well for test management and is a good testing repository."
"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 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."
"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'm looking at more towards something more from a DevOps perspective. For example, how to pull the DevOps ecosystem into the Micro Focus ALM."
"The performance could be faster."
"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."
"Micro Focus ALM Quality Center should improve the reports. Reporting on tax execution progress against the plan. However, they might have improved over two years since I have used the solution."
"The BPT also known as Business Process Testing can sometimes be very time intensive and sometimes might not be very intuitive to someone who is not familiar with BPT."
"There's room for improvement on the reporting side of things and the scheduling, in general, is a bit clunky."
"The product is good, it's great, but when compared to other products with the latest methodologies, or when rating it as a software development tool, then I'll have to rate it with a lower score because there's a lot of other great tools where you can interconnect them, use them, scale them, and leverage. It all depends on the cost."
"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."
"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."
"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."
"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."
"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."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"Could use additional integration so that there is a testing automation continuum."
"The support for Tricentis qTest has room for improvement. The response could be better."
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.