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

"For what I need TFS for, I have never run into any limitation."
"Work item management integration with source control."
"The most valuable feature of TFS is that it keeps the code secure while working collaboratively in a team of four or five individuals."
"A notable feature of TFS is its ease of creating user stories and tasks, which simplifies the process of adding and editing them."
"We use TFS for forecast management."
"Complete integration with VS IDE and Office tools: This give us a possibility of high-level automation, thus minimizing human error."
"The work item feature is most valuable. It allows us to store all product requirements. We can also link the test cases to those requirements so that we know which feature has already been tested, and which one is waiting for testing. We can also couple the code reviews, unit tests, and automated tests into these requirements. It is reliable. It has all the features and good performance. It also has reporting tools or analysis tools."
"TFS' most valuable feature is the triage process. It is a robust solution that is easy to use."
"The solution's real-time integration with JIRA is seamless."
"The initial setup was very easy."
"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."
"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."
"The integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"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."
"The self-healing aspects and maintenance of scripts are much faster and quicker, and we are able to find better avenues and better productivity in terms of maintenance, which we can pass on to the customer."
"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."
 

Cons

"TFS isn't a great tool if you're on the cloud."
"Integration from Visual Studio could be improved."
"There is room for improvement from reporting point of view."
"In the next release, I would like them to include integration for various projects, similar to what JIRA has, and they could create this feature on the dashboard."
"The price could be cheaper."
"Not all of the functionality, which is exposed by the command line interface (tf.exe) is available in the Visual Studio GUI."
"The user interface could improve and test management was not useful in TFS."
"Microsoft should discontinue the use of SharePoint as I don’t really see any value add to TFS, document management features can be included in TFS web portal itself, if required!"
"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 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."
"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."
"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."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"The support for Tricentis qTest has room for improvement. The response could be better."
 

Pricing and Cost Advice

"It is an expensive solution."
"The solution is expensive."
"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."
"Microsoft products are always expensive. Obviously, they are quality products, but it would be helpful if there was a reduction in price. But compared to other vendors, I think the cost is high."
"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."
"You will need to obtain server and account licenses."
"We pay subscription fees on a yearly basis and the price is reasonable."
"It's just as expensive as HPE ALM, without many of the features, best used for development tool only to avoid higher costs."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"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."
"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 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."
"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.
867,676 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
13%
Manufacturing Company
11%
Financial Services Firm
10%
Healthcare Company
7%
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,676 professionals have used our research since 2012.