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

IBM Engineering Test Management 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

IBM Engineering Test Manage...
Ranking in Test Management Tools
7th
Average Rating
7.6
Reviews Sentiment
7.4
Number of Reviews
11
Ranking in other categories
Load Testing Tools (11th)
Tricentis qTest
Ranking in Test Management Tools
4th
Average Rating
8.4
Reviews Sentiment
7.5
Number of Reviews
16
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2025, in the Test Management Tools category, the mindshare of IBM Engineering Test Management is 2.8%, down from 2.9% compared to the previous year. The mindshare of Tricentis qTest is 16.4%, up from 10.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools
 

Featured Reviews

HZ
Scalable and Stable solution with good integration function and support team
IBM Rational has the RFT, which is rational functional testing. We do test automation with rational functional testing. So after we do that, we can put in all the code, then I can build it, then put all the test cases, and put all the build code for the shared location. And then rational that shared location means that RQM has access to the shared location. So, when we execute, if a test case is automated, we can run it from RQM. We need to have the environment ready for it to execute. Once we have that, then we can select the task case. So, by clicking on one button, the other environment is automatically plugged in. Then test results will be automatically transferred back to our RQM. So, in RQM, we can view it, and it is integrated. So we can run the test and the automation from RQM, and the test results will come back. Azure DevOps first test case is there, but then we tried to use Selenium to do half automation. Still, we realized that it wouldn't have the integration. We could do something in the pipeline, but it fires the Selenium test automation code. But then the test results won't be brought back or added to AzureDesk DevOps. That's something that I do hope that there can be another other system that can have this kind of integration. RQM can be improved because it's not related to our server and could be faster. We need to find out how much database storage is needed and keep increasing it. We heard that the latest version of RQM can clean up some old ones and give the same test result. But that one feature we are yet to use. It's a setting that we can set up, and then it goes automatically or gives me the choice to do it manually.
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

"RQM's best features are integration with test automation and performance testing."
"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."
"The most valuable feature is the RFT because it allows us to automate manual test cases."
"It's very reliable as a solution."
"Latest features include versioning of testings which can be great when used for multiple releases of a product."
"It allows user to add whichever widget (predefined) based on the need. It has integration with CCM and RM to achieve traceability."
"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 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..."
"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."
"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."
"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."
"UI and UX are pretty easy to understand without much of a problem."
 

Cons

"While RQM allows for running tests and viewing results, it could be further enhanced in terms of performance and speed."
"I think it's fine from a performance perspective but usability is something that needs improvement."
"Mainly Quality Assurance and DevOps, but of course the whole company and management areas with more knowledge of quality and client success approach."
"Integration capabilities with other vendors' tools should improve."
"Adding support for uploading a collection of test cases would be a helpful addition."
"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."
"It would be helpful if we could assign a hierarchy to a group of test cases."
"Could use additional integration so that there is a testing automation continuum."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"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."
"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."
"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."
"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."
"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."
 

Pricing and Cost Advice

"Each license includes 12 months of customer support. A free 90-day trial of the software is also available."
"The licenses of these tools (the whole CLM package) is very costly as compared to other vendors' tools."
"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."
"Our license price point is somewhere between $1,000 and $2,000 a year."
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"We're paying a little over $1,000 for a concurrent license."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"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 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."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
832,138 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Healthcare Company
19%
Manufacturing Company
15%
Computer Software Company
13%
Financial Services Firm
13%
Financial Services Firm
14%
Manufacturing Company
12%
Computer Software Company
12%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about IBM Rational Quality Manager?
The one feature that has not allowed us to switch to any other solution is the integration with functional testing.
What needs improvement with IBM Rational Quality Manager?
IBM Rational has the RFT, which is rational functional testing. We do test automation with rational functional testing. So after we do that, we can put in all the code, then I can build it, then pu...
What is your primary use case for IBM Rational Quality Manager?
We create test cases, and then we need to plan a new task plan feature from the existing task case file and execute the test results, which will be saved in RQM. So that is how we are using the too...
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?
The user interface has a somewhat outdated design, which is certainly an area that could be improved. Some of the modules appear to be loosely connected, but despite these aspects, our overall expe...
 

Also Known As

IBM Rational Quality Manager, Rational Quality Manager
qTest
 

Overview

 

Sample Customers

Ehrhardt, Cisco Systems, Anadolu Hayat Emeklilik, CareCore National, ItaÒ BBA, Barr
McKesson, Accenture, Nationwide Insurance, Allianz, Telstra, Moët Hennessy-Louis Vuitton (LVMH PCIS), and Vodafone
Find out what your peers are saying about IBM Engineering Test Management vs. Tricentis qTest and other solutions. Updated: January 2025.
832,138 professionals have used our research since 2012.