Try our new research platform with insights from 80,000+ expert users

OpenText ALM / Quality Center vs Tricentis qTest comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 16, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

OpenText ALM / Quality Center
Ranking in Test Management Tools
1st
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
207
Ranking in other categories
Application Lifecycle Management (ALM) Suites (4th)
Tricentis qTest
Ranking in Test Management Tools
4th
Average Rating
8.2
Reviews Sentiment
7.5
Number of Reviews
17
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2025, in the Test Management Tools category, the mindshare of OpenText ALM / Quality Center is 13.7%, up from 13.0% compared to the previous year. The mindshare of Tricentis qTest is 16.9%, up from 10.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools
 

Featured Reviews

Paul Grossman - PeerSpot reviewer
Range of supported technology expands, but odd IDE design still leave newbies and pro users alike disappointed.
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. While I have a larger list of issues that make day to day work harder than it needs to be, these are the Top Five that I do wish would capture someone's attention in upcoming releases. All hit the tool's ROI pretty hard. #1) Jump To Source - The Silent Code Killer: In older QTP versions a double-click on any function in the Toolbox window would take the developer to the function's source code, while a drag from the Toolbox would add it to the code window. Since 12.0 a double-click on a function in UFT's Toolbox window now ADDS the function (same as drag) to the Code window - to whatever random location the cursor happens to be at - even if it is off screen, and it will replace sections of code if it is highlighted. We are not sure what the intention was, but our Best Practice is to avoid the Toolbox window entirely to avoid the real danger of losing days of work and needless bug hunts. Now Jump to Source is not all bad. A right-click on any function called from a Script takes us to the code source, which is great! But it only half works: in a Library, only for functions declared within the same library. Our advance designs have well over twelve libs so a whole lot of extra time is spent searching the entire project for a function's source on a daily basis. Lastly, while we can add custom methods to object, a Jump To Source from these methods is long overdue. So again our only option is to search the entire project. #2) Object Spy: It needs to have multiple instances so that you can compare multiple object properties side-by-side. It lacks a Refresh button, so that automation engineers can quickly identify the property changes of visible and invisible objects. Or HP could skip to option #3... #3) Add RegEx integer support for .Height or .Width object properties when retrieving object collections. If this were possible, our framework could return collections that contain only visible objects that have a .height property greater that zero. (Side Note: the .Visible property has not returned a False value for us in nearly five years - a recent developer decision, not a product issue) Eliminating the need to separate the non-visible objects from visible ones would decrease execution time dramatically. (Another side note: Our experiments to RegEx integer-based .Height properties found that we could get a collection of just invisible objects. Exactly the opposite of what we needed.) #4) The shortcut to a treasure trove of sample code in the latest release 14.0 has been inexplicably removed. This impeeds new users from having an easy time learning the tool's advanced capability. In fact the only users daring enough to go find it now will be you who is reading this review. #5) Forced Return to Script Code. This again is a no-brainer design flaw. Let's say we run a script and throw an error somewhere deep in our function library. Hey it happens. In prior QTP versions when the Stop button would be clicked the tool would leave you right there at the point where the error occurred to fix. Now in recent releases, UFT always takes us back to the main Script, far from that code area that needed immediate attention.
Sudipto Dey - PeerSpot reviewer
It doesn't require installation because you can use it through the URL; it's user-friendly and has an excellent reporting feature
The support for Tricentis qTest has room for improvement. The response could be better. There's a feature I want to document on the Tricentis Idea Portal for Tricentis qTest, which I hope to see in the next version of the tool. It's a feature available in Micro Focus where you execute a test, and then on a spec level, you mark it as pass or fail. Then at the overall level, Micro Focus will automatically mark the test as a pass if all steps passed or failed, even if one step failed. However, here in Tricentis qTest, you still need to mark the overall level of the test cases. It's not automated, unlike what you have in Micro Focus. If Tricentis adds that feature in Tricentis qTest, it will make life easier for testers.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"I like that it integrates with the Jira solutions."
"Cross project customization through template really helps to maintain standards with respect to fields, workflows throughout the available projects."
"We can create a requirement for stability metrics with the test cases to ensure all requirements are covered."
"It was really good, customizable, and easy to use."
"As a stand-alone test management tool, it's a good tool."
"Test Execution (Test Lab): This allows us to track our manual tests with date and time and enter actual results and screenshots."
"Defect management is very good."
"Easily integrates with Oracle e-Business Suite."
"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 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."
"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 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."
"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."
"UI and UX are pretty easy to understand without much of a problem."
"The solution's real-time integration with JIRA is seamless."
"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..."
 

Cons

"Defect ageing reports need to be included as built-in."
"Micro Focus ALM Quality Center could improve how the automation process works. Addiotnlally, the parallel execution needs to be optimized. For example, if multiple users, which are two or more users, are doing an execution, while we execute the cases, I have seen some issues in the progress."
"We cannot rearrange the Grid in the Test Lab. It is in alphabetical order right now. But sometimes a user will want to see, for example, the X column next to the B column. If they came out with that it would be useful for us. They are working on that, as we have raised that request with Micro Focus."
"We have had a poor experience with customer service and support."
"Return on investment isn't something I often contemplate. I have not seen many business cases around it."
"There needs to be improvement in the requirement samples. At the moment, they are very basic."
"We operate in Sweden, and there are not so many Swedish people that know the product."
"Currently, what's missing in the solution is the ability for users to see the ongoing scenarios and the status of those scenarios versus the requirements. As for the management tools, they also need to be improved so users can have a better idea of what's going on in just one look, so they can manage testing activities better."
"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."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"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 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."
"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."
"Could use additional integration so that there is a testing automation continuum."
 

Pricing and Cost Advice

"This is an expensive solution."
"The solution was expensive for us."
"Most vendors offer the same pricing, though some vendors offer a cheaper price for their cloud/SaaS solution versus their on-premise. However, cloud/SaaS solutions result in a loss of freedom. E.g., if you want to make a change, most of the time it needs to be validated by the vendor, then you're being charged an addition fee. Sometimes, even if you are rejected, you are charged because it's a risk to the entire environment."
"For pricing, I recommend to buy a bundled package. Check the HPE site for more details."
"It all comes down to how many people are going to access the tool. When teams go above 20, I think ALM is a better tool to use from a collaboration and streamlining perspective."
"ALM Quality Center is a little bit costly."
"Micro Focus ALM Quality Center is very expensive. The price is approximately £2,000 per person, they are too expensive to corner the market."
"The pricing is expensive nowadays."
"We signed for a year and I believe we paid $24,000 for Flood, Manager, and the qTest Insights. We paid an extra for $4,000 for the migration support."
"It's quite a few times more costly than other tools on the market."
"Based on whatever I heard, I can say that Tricentis qTest is a little costlier than other test management tools, like Jira, Zephyr, or Xray."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"Our license price point is somewhere between $1,000 and $2,000 a year."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"For me, pricing for Tricentis qTest is moderate, so that's a five out of ten. It's more affordable than my company's previous solution, which was Micro Focus ALM."
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
841,004 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
67%
Financial Services Firm
6%
Manufacturing Company
5%
Computer Software Company
4%
Financial Services Firm
13%
Manufacturing Company
12%
Computer Software Company
11%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Micro Focus ALM Quality Center?
The most valuable feature is the ST Add-In. It's a Microsoft add-in that makes it much easier to upload test cases into Quality Center.
What is your experience regarding pricing and costs for Micro Focus ALM Quality Center?
The on-premises setup tends to be on the expensive side. It would be cheaper to use a cloud model with a pay-per-use licensing model.
What needs improvement with Micro Focus ALM Quality Center?
We work with Jira now, and there are some very good workflows. There could be more configurable workflows regarding test case creation approval. I see a stable tool that remains relevant in the mar...
What do you like most about Tricentis qTest?
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 is your experience regarding pricing and costs for Tricentis qTest?
Based on whatever I heard, I can say that Tricentis qTest is a little costlier than other test management tools, like Jira, Zephyr, or Xray.
What needs improvement with Tricentis qTest?
Tricentis qTest needs improvement in its repositories' functionality. Unlike Azure, it does not have repositories to upload scripts. Additionally, it lacks features like task addition and tracking ...
 

Also Known As

Micro Focus ALM Quality Center, HPE ALM, Quality Center, Quality Center, Micro Focus ALM
qTest
 

Overview

 

Sample Customers

Airbus Defense and Space, Vodafone, JTI, Xellia, and Banco de Creìdito e Inversiones (Bci)
McKesson, Accenture, Nationwide Insurance, Allianz, Telstra, Moët Hennessy-Louis Vuitton (LVMH PCIS), and Vodafone
Find out what your peers are saying about OpenText ALM / Quality Center vs. Tricentis qTest and other solutions. Updated: January 2025.
841,004 professionals have used our research since 2012.