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 (4th)
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 January 2025, in the Test Management Tools category, the mindshare of TFS is 8.6%, down from 11.1% compared to the previous year. The mindshare of Tricentis qTest is 16.4%, up from 9.9% 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."
"Build definitions and releases within the product. allow us to put our latest applications in the field."
"The tool's installation is straightforward."
"The most valuable feature of TFS is the central repository, and you can see what changes other developers did from which branch."
"I like the build management features and the integration with Jenkins and many other tools."
"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."
"I like its MTM (Microsoft Test Manager) section which gives us options to create various test plans and add test cases into it."
"Version Control: TFS offers both the centralized “TFVC” version control technology as well as the distributed “Git” version control technology."
"UI and UX are pretty easy to understand without much of a problem."
"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 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 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..."
"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."
"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 dashboard needs more enhancements."
"The interface can be improved and made more user-friendly."
"The tool needs improvement in stability."
"As an end-user, I expect the solution's performance to be faster while staying as stable as possible."
"The usability of TFS is not that great."
"TFS's CI/CD, project pipelines, and management development could be improved."
"I would also like a true command prompt like Git."
"The test management interface is not very handy."
"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."
"Could use additional integration so that there is a testing automation continuum."
"The support for Tricentis qTest has room for improvement. The response could be better."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from 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."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"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."
"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."
 

Pricing and Cost Advice

"I believe we pay on a yearly basis. I don't know the current costs of them. We outsource all that to a third party. Each of the developers gets a Microsoft Visual Studio Azure DevOps license, which gives them access to the TFS server as well. We probably pay on average about 1,800 Canadian Dollars a year for every developer, but that covers a lot more than just TFS."
"We are using the open-source version."
"If running TFS on-premise is expensive, maybe you could consider moving to the Cloud and use the Visual Studio Team Services."
"You will need to obtain server and account licenses."
"It is an expensive solution."
"Use the Microsoft recommended “seat-based” licensing model. This allows a single developer with multiple machines to consume only one client license."
"The price of the solution is cheaper than other competitors and it is a per-user license."
"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."
"We're paying a little over $1,000 for a concurrent license."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"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."
"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 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."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"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.
831,158 professionals have used our research since 2012.
 

Top Industries

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

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?
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...
 

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: January 2025.
831,158 professionals have used our research since 2012.