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.4
Reviews Sentiment
7.5
Number of Reviews
16
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
51
Ranking in other categories
Functional Testing Tools (5th)
 

Mindshare comparison

As of January 2025, in the Test Management Tools category, the mindshare of Tricentis qTest is 16.4%, up from 9.9% compared to the previous year. The mindshare of Visual Studio Test Professional is 3.1%, down from 5.6% 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.
CharlesChang - PeerSpot reviewer
Valuable performance and libraries but needs compatibility improvements
We use Visual Studio Test Professional to develop our internal applications for our company The performance of Visual Studio Test Professional is valuable. Additionally, there are many libraries that I can use, and it supports cross-platform functionality. Visual Studio Test Professional is…

Quotes from Members

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

Pros

"The solution's real-time integration with JIRA is seamless."
"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 integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"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."
"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 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."
"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."
"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."
"You can easily write code, test, and deploy within the same environment. It is a mature tool. It regularly receives new updates and versions. In my opinion, it's one of the best products by Microsoft for developers."
"The debugging feature is valuable."
"The most valuable features are the SSIS reports, the deployment models, and the ability to interact with other Microsoft tools."
"It is very easy to use. You can handle a lot of things together at once in one package, which is a good point for us."
"The performance of Visual Studio Test Professional is valuable."
"The product is good to create big or small projects fastly. It is one of the leaders in the area."
"The most valuable features of the solution are its ease of use and availability."
"The solution is very stable."
 

Cons

"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 support for Tricentis qTest has room for improvement. The response could be better."
"Could use additional integration so that there is a testing automation continuum."
"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."
"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."
"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."
"Visual Studio Test Professional needs to improve its stability."
"It is not good in terms of performance. When you open Visual Studio, you have to wait for a while to process your code. It uses a lot of resources and has a lot of features. If we could disable some of the features, it would be lighter and faster to use. Nowadays, for some of the projects, we use VS Code for JavaScript or Python. VS Code is very light and easy to use, whereas, in Visual Studio, we have to wait because it takes time to compile or run a project. It has a lot of competitors in terms of performance, such as Intelligent ID. Intelligent ID is very easy to use. It has many features, and it is lighter to use than Visual Studio. In terms of error handling, sometimes, it shows an error before you finish your code, which can be improved. It would be good if it has a version for Linux. I use VS Code on Linux, but I am not sure if Visual Studio has a version for Linux."
"Visual Studio Test Professional is expensive."
"The product must provide more integration."
"The product must provide more automation."
"The integration with Git needs improving because it is a bit disjointed and unpredictable."
"The solution is quite expensive."
"I would appreciate some enhancements in the interface, maybe adding more color options."
 

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."
"Our license price point is somewhere between $1,000 and $2,000 a year."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"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."
"It's quite a few times more costly than other tools on the market."
"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."
"We're paying a little over $1,000 for a concurrent license."
"I think that the pricing is quite good."
"Our company pays a yearly licensing fee for Visual Studio Test Professional."
"We pay a yearly licensing fee for Visual Studio Test Professional, which is expensive."
"We use the solution’s community version, and the solution’s pricing could be cheaper."
"It is a price-effective solution"
"The product is very expensive."
"I positioned it at a mid-range level. It isn't an inexpensive solution, but considering its capabilities, it represents excellent value for the functionalities it offers."
"The tool is expensive in my region."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
831,265 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Manufacturing Company
12%
Computer Software Company
11%
Insurance Company
7%
Financial Services Firm
19%
Computer Software Company
16%
Manufacturing Company
8%
Government
6%
 

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?
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...
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?
There are not any specific areas for improvement since there are so many libraries and frameworks already available, and we have not even touched everything yet.
 

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