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
4th
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
99
Ranking in other categories
Application Lifecycle Management (ALM) Suites (6th)
Tricentis qTest
Ranking in Test Management Tools
3rd
Average Rating
8.4
Reviews Sentiment
7.5
Number of Reviews
18
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of September 2025, in the Test Management Tools category, the mindshare of TFS is 6.3%, down from 9.2% compared to the previous year. The mindshare of Tricentis qTest is 14.6%, up from 12.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools Market Share Distribution
ProductMarket Share (%)
Tricentis qTest14.6%
TFS6.3%
Other79.1%
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…
SamuLehikoinen - PeerSpot reviewer
Efficient and collaborative software testing providing comprehensive test management capabilities, seamless integration with various tools and impressive manual regression testing features
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 experience with the tool was positive. When you begin integrating your testing tools with qTest, the available examples may not be very clear, and I believe this is an area that could be enhanced, particularly in terms of providing clearer integration guidance. While the tool's integration with various testing tools is impressive, there is room for improvement in showcasing more cases and benefits, especially through additional videos and documentation.

Quotes from Members

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

Pros

"It's user friendly. We haven't had any issues so far. It's flexible. If we need something, we can always contact the owner in our headquarters to make a configuration."
"The most valuable feature is the backlog."
"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 most valuable features of TFS are the test plans. We can reproduce reusable test plans in test automation. We have a lot of queries and this feature is very useful."
"Good branching and labelling features."
"TFS's best features include user-friendly test management, bug reporting, and ID assignment."
"Team Foundation Server (TFS) is easy to use, and we have a complete trail and traceability. We also like the access control part."
"The traceability is valuable. While managing the workflows, it was always nice to have that traceability from requirements and all the way through design. It integrates with Microsoft Test Manager, and you can have everything that is related to a requirement attached to it."
"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..."
"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 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."
"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."
"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."
"Works well for test management and is a good testing repository."
"The integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"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."
 

Cons

"The price could be cheaper."
"The execution of test cases could stand improvement."
"The user interface could improve and test management was not useful in TFS."
"Overall, I think it would be useful to have something similar where Microsoft comes up with supporting concepts of scaling Agile in TFS so that clients don't have to look for a separate tool."
"Currently, we are looking for a solution with which we can incorporate third-party development sites or third-party project teams into the system. Because it is on-premise, it is a bit problematic because we need to have a VPN or something else in the system. A cloud-based solution would be better for us, and that's what we are looking for. Our biggest problem is the external connection, which, of course, is limited by our own IT. It would be good to have some kind of publishing service for this external connection. It might be there, and it might be that our IT is making it impossible for us. Its template editor could be easier to use. Currently, customizing the project templates according to your needs requires some work."
"They have room for improvement in merging the source code changes for multiple developers across files. It is very good at highlighting the changes that the source code automatically does not know how to handle, but it's not very good at reporting the ones that it did automatically. There are times when we have source code that gets merged, and we lose the changes that we expected to happen. It can get a little confusing at times. They can just do a little bit better on the merging of changes for multiple developers."
"The reporting functionality is something that they should work on."
"I'm looking for specific options that aren't currently available, such as active status, new status, or what's currently in progress."
"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."
"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."
"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."
"We faced challenges when trying to consolidate data in a repository, and similar features were lacking in qTest. It also does not allow for task tracking or calculating time spent on tasks, which affects project timelines."
"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."
"Could use additional integration so that there is a testing automation continuum."
"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."
 

Pricing and Cost Advice

"It is pretty expensive compared to other project management tools."
"The tool's licensing costs are yearly."
"I wouldn't say that this tool is cheap or expensive but in the middle."
"TFS is on the higher side, but if you intend to use the tool as a complete ALM tool, it will reduce your costs in the long run."
"I was working with the engineering team, and that was not under my umbrella. From what I can remember, its license was yearly. They had the licenses on a per-user basis, and they included MTM."
"It is an expensive solution."
"We pay subscription fees on a yearly basis and the price is reasonable."
"The overall price of TFS is good."
"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 a little over $1,000 for a concurrent license."
"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."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"It's quite a few times more costly than other tools on the market."
"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."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"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.
867,370 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
13%
Manufacturing Company
12%
Financial Services Firm
10%
Healthcare Company
8%
Financial Services Firm
14%
Manufacturing Company
12%
Computer Software Company
10%
Insurance Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise25
Large Enterprise64
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise13
 

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?
The solution is expensive. For the features that are available, depending on the volumes of licenses we get, we are able to get better discounts as strategic partners of Tosca. We can pass some ben...
What needs improvement with Tricentis qTest?
Customers are moving towards Tricentis due to their association with SAP. There is interest in understanding if there are connectors for converting UFT scripts to Tosca, as many customers are looki...
 

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: September 2025.
867,370 professionals have used our research since 2012.