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

Tricentis qTest vs Visual Studio Test Professional 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

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
Visual Studio Test Professi...
Ranking in Test Management Tools
5th
Average Rating
8.4
Reviews Sentiment
7.2
Number of Reviews
52
Ranking in other categories
Functional Testing Tools (6th)
 

Mindshare comparison

As of April 2025, in the Test Management Tools category, the mindshare of Tricentis qTest is 16.1%, up from 10.7% compared to the previous year. The mindshare of Visual Studio Test Professional is 2.5%, down from 4.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools
 

Featured Reviews

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.
ALFONSO LORENZO-RODRÍGUEZ - PeerSpot reviewer
Provides extensive extensions and plugins for seamless AI product development
Our primary use case for Visual Studio Test Professional is as a development tool. We develop software primarily in Python, specifically for applications related to artificial intelligence. We use frameworks like PyTorch for training models and developing applications using these models. This tool…

Quotes from Members

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

Pros

"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 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."
"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."
"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 integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"The solution's real-time integration with JIRA is seamless."
"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 valuable features are the SSIS reports, the deployment models, and the ability to interact with other Microsoft tools."
"The interface is easy to use."
"The most valuable feature of Visual Studio Test Professional is its ease of use."
"Visual Studio is highly powerful. It's probably the best software development tool on the market."
"Visual Studio is the easiest to use."
"Easy to use and easily scalable."
"Visual Studio Test Professional is highly valuable because it provides extensive extensions and plugins that assist in measuring code quality."
"The debugging feature is valuable."
 

Cons

"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."
"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."
"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."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"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."
"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."
"Sometimes, the solution hangs, so its performance could be improved."
"The solution can improve the startup time."
"It would be great to support other languages and applications, and that is one of the things we can improve."
"The documentation is limited."
"In Visual Studio we still don't have anything which can pinpoint memory leaks on a certain code line."
"The service right now is far too expensive. You need to pay per user."
"The tool crashes and has high memory consumption."
"One of the problems with this solution is you need to be highly technically skilled to operate it, it is not for everyone."
 

Pricing and Cost Advice

"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
"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."
"It's quite a few times more costly than other tools on the market."
"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."
"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."
"For the cloud services option, you buy a subscription per account or per user. This costs around $52 a month per person."
"It is a price-effective solution"
"There are two versions of Visual Studio Test Professional: Community and Professional. We are currently using the Community version, but if we start working on a commercial product, we will consider upgrading to the Professional version. We need to identify how we will proceed with our projects, and based on that, we will decide on our licensing."
"Our company pays a yearly licensing fee for Visual Studio Test Professional."
"Visual Studio Test Professional is a very expensive solution."
"Users have to pay a licensing fee for Visual Studio Test Professional."
"The product is very expensive."
"The tool is affordable."
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
Financial Services Firm
13%
Computer Software Company
12%
Manufacturing Company
11%
Insurance Company
8%
Financial Services Firm
21%
Computer Software Company
17%
Manufacturing Company
9%
Real Estate/Law Firm
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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 ...
What do you like most about Visual Studio Test Professional?
The most valuable features of the solution are its ease of use and availability.
What is your experience regarding pricing and costs for Visual Studio Test Professional?
The tool is free, resulting in no costs associated with its use. The absence of price makes it cost-effective.
What needs improvement with Visual Studio Test Professional?
The product needs contextual help integrated within its interface. Currently, I need to search online to find out how to use certain functions. This feature would save time by providing direct assi...
 

Also Known As

qTest
No data available
 

Overview

 

Sample Customers

McKesson, Accenture, Nationwide Insurance, Allianz, Telstra, Moët Hennessy-Louis Vuitton (LVMH PCIS), and Vodafone
Transport for Greater Manchester, Ordina, Bluegarden A/S, CLEAResult, Jet.com, OSIsoft, Australian Taxation Office, BookedOut, Tracasa
Find out what your peers are saying about Tricentis qTest vs. Visual Studio Test Professional and other solutions. Updated: March 2025.
845,406 professionals have used our research since 2012.