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

TFS 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

TFS
Ranking in Test Management Tools
3rd
Average Rating
8.0
Reviews Sentiment
7.1
Number of Reviews
98
Ranking in other categories
Application Lifecycle Management (ALM) Suites (5th)
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 April 2025, in the Test Management Tools category, the mindshare of TFS is 7.5%, down from 10.9% compared to the previous year. The mindshare of Tricentis qTest is 16.1%, up from 10.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools
 

Featured Reviews

Pmurki@Micron.Com Praveen - PeerSpot reviewer
Version control is excellent and good for code review, branching, merging strategies and more
I've worked with TFS for source control and Agile project management. We also used TFS for seamless team collaboration and tracking.  I used TFS for a couple of years. Now, we use Azure DevOps. It's a wonderful tool for source control and CI/CD pipelines It's a really valuable tool for…
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 have found almost all of the features valuable because it integrates well with your Microsoft products. If a client is using the entire Microsoft platform, then TFS would be definitely preferable. It integrates with the digital studio development environment as well."
"The most valuable feature is simplicity."
"Once TFS is installed, there are no major issues."
"Build definitions and releases within the product. allow us to put our latest applications in the field."
"I like the Kanban board. It is very useful in terms of seeing who is working on what and what the current status of work is."
"The initial setup is easy, it is easy to understand and use."
"The most valuable feature is integration, particularly if you have a .NET application."
"Complete integration with VS IDE and Office tools: This give us a possibility of high-level automation, thus minimizing human error."
"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."
"UI and UX are pretty easy to understand without much of a problem."
"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."
"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."
"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 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."
"The initial setup was very easy."
 

Cons

"The usability of TFS is not that great."
"I would like to see TFS improve its web interface as there are some limitations with IDs and the integration behind it and with open-source tools like VS Code."
"The user interface could be improved to make it simpler and increase usability."
"I'd like to see some kind of visualization tool for TFS that would make life much easier."
"There's not automatic access to test case management and execution."
"TFS should have capabilities similar to Git, like storing all types of artifacts in the repository."
"We are also using Microsoft Teams. The two products function separately. There is not enough collaboration between Microsoft Teams and TFS."
"TFS needs to be stable."
"I wouldn't say a lot of good things about Insights, but that's primarily because, with so many test cases, it is incredibly slow for us. We generally don't use it because of that."
"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."
"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 support for Tricentis qTest has room for improvement. The response could be better."
"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."
"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."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"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

"It is an expensive solution."
"We pay subscription fees on a yearly basis and the price is reasonable."
"I would like to see TFS improve its web interface as there are some limitations with IDs and the integration behind it and with open source tools like VS Code."
"TFS is more competitively priced than some other solutions."
"I am not in a position to comment on the licensing terms, as we are talking about an enterprise arrangement."
"On a scale where ten is the highest and one is the cheapest, I rate the solution's licensing cost at one on a scale of one to ten."
"There are different prices depending on the configurations. There is a free version available. There is no extra cost for the solution. However, the hardware could be something that needs to be considered."
"TFS is not cheap."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"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."
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
"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."
"We're paying a little over $1,000 for a concurrent license."
"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."
"Our license price point is somewhere between $1,000 and $2,000 a year."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
68%
Computer Software Company
5%
Financial Services Firm
4%
Manufacturing Company
3%
Financial Services Firm
13%
Computer Software Company
12%
Manufacturing Company
11%
Insurance Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Which is better - TFS or Azure DevOps?
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very fri...
What do you like most about TFS?
Microsoft's technical team is supportive.
What is your experience regarding pricing and costs for TFS?
While I do not know the exact pricing, TFS is likely more expensive than GitLab.
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 ...
 

Comparisons

 

Also Known As

Team Foundation Server
qTest
 

Overview

 

Sample Customers

Vendex KBB IT Services, Info Support, Fujitsu Consulting, TCSC, Airways New Zealand, HP
McKesson, Accenture, Nationwide Insurance, Allianz, Telstra, Moët Hennessy-Louis Vuitton (LVMH PCIS), and Vodafone
Find out what your peers are saying about TFS vs. Tricentis qTest and other solutions. Updated: March 2025.
845,406 professionals have used our research since 2012.