Compare Tricentis qTest vs. Visual Studio Test Professional

Cancel
You must select at least 2 products to compare!
Top Review
Find out what your peers are saying about Tricentis qTest vs. Visual Studio Test Professional and other solutions. Updated: September 2021.
536,053 professionals have used our research since 2012.
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 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.""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.""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 integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good.""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 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."

More Tricentis qTest Pros »

"Code testing is the most valuable feature of this solution for developing software.""The setup is easy and straightforward.""The solution is very stable; there's nothing in relation to stability to complain about.""The most valuable features are the SSIS reports, the deployment models, and the ability to interact with other Microsoft tools.""The most valuable feature is the in-built support for C# and .NET projects.""Performance-wise, it is a great tool.""The most valuable features are tools like IntelliSense and ReSharper.""It is a very common and strong product. A lot of support is available for this product."

More Visual Studio Test Professional Pros »

Cons
"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.""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.""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 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.""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 Insights reporting engine has a good test-metrics tracking dashboard. The overall intent is good... But the execution is a little bit limited... the results are not consistent. The basic premise and functionality work fine... It is a little clunky with some of the advanced metrics. Some of the colorings are a little unique.""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.""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."

More Tricentis qTest Cons »

"Enhancing the support for web application testing and load performance would be an improvement.""The data flow can be improved.""The database administration could be better; you should be able to choose new tools with the development environment in Visual Studio. It could be easier to use.""The documents on the Microsoft website are not very useful, and they ought to make it easier to find answers.""We would like to be able to easily integrate this solution with our continuous integration tools, such as Jenkins.""The pricing of this solution should be lowered.""The integration with Git needs improving because it is a bit disjointed and unpredictable.""It needs more integration with other tools for monitoring. Microsoft also needs to make it more modern to make it work with microservices and the cloud. It is a bit outdated currently."

More Visual Studio Test Professional Cons »

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.""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.""We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that.""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."

More Tricentis qTest Pricing and Cost Advice »

"I think that the pricing is quite good.""The pricing is expensive."

More Visual Studio Test Professional Pricing and Cost Advice »

report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
536,053 professionals have used our research since 2012.
Questions from the Community
Top Answer: First, I would ask what your testing process is and are you a Dev/Ops shop or other methodology?  The QTest tool is both a good manual testing tool and with Tosca you can automate your testing as… more »
Top Answer: The stability has always been very good.
Top Answer: We aren't bothered by the pricing of the solution at all due to the fact that it provides us with a lot of great tools. The pricing is high, however, it's a single tool that allows you to do a lot of… more »
Top Answer: In Visual Studio we still don't have anything which can pinpoint memory leaks on a certain code line. It gives me memory analysis, however, it's not taking me to the code lines. That's what I was… more »
Ranking
3rd
Views
7,232
Comparisons
3,283
Reviews
10
Average Words per Review
2,074
Rating
8.4
4th
Views
3,121
Comparisons
2,480
Reviews
12
Average Words per Review
365
Rating
8.4
Comparisons
Also Known As
qTest
Learn More
Overview

Tricentis is the global leader in enterprise continuous testing, widely credited for reinventing software testing for DevOps, cloud, and enterprise applications. The Tricentis AI-based, continuous testing platform provides a new and fundamentally different way to perform software testing. An approach that’s totally automated, fully codeless, and intelligently driven by AI. It addresses both agile development and complex enterprise apps, enabling enterprises to accelerate their digital transformation by dramatically increasing software release speed, reducing costs, and improving software quality. 

Visual Studio Professional Edition provides an IDE for all supported development languages. As of Visual Studio 2010, the Standard edition was dropped. MSDN support is available as MSDN Essentials or the full MSDN library depending on licensing. It supports XML and XSLT editing, and can create deployment packages that only use ClickOnce and MSI. It includes tools like Server Explorer and integration with Microsoft SQL Server also. Windows Mobile development support was included in Visual Studio 2005 Standard, however, with Visual Studio 2008, it is only available in Professional and higher editions. Windows Phone 7 development support was added to all editions in Visual Studio 2010. Development for Windows Mobile is no longer supported in Visual Studio 2010; it is superseded by Windows Phone 7.
Offer
Learn more about Tricentis qTest
Learn more about Visual Studio Test Professional
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
Top Industries
REVIEWERS
Computer Software Company29%
Energy/Utilities Company14%
Healthcare Company14%
Financial Services Firm14%
VISITORS READING REVIEWS
Computer Software Company32%
Comms Service Provider14%
Financial Services Firm8%
Insurance Company7%
REVIEWERS
Computer Software Company36%
Manufacturing Company18%
Transportation Company9%
Healthcare Company9%
VISITORS READING REVIEWS
Computer Software Company30%
Comms Service Provider20%
Financial Services Firm8%
Government7%
Company Size
REVIEWERS
Small Business8%
Midsize Enterprise25%
Large Enterprise67%
VISITORS READING REVIEWS
Small Business15%
Midsize Enterprise10%
Large Enterprise76%
REVIEWERS
Small Business12%
Midsize Enterprise18%
Large Enterprise71%
Find out what your peers are saying about Tricentis qTest vs. Visual Studio Test Professional and other solutions. Updated: September 2021.
536,053 professionals have used our research since 2012.

Tricentis qTest is ranked 3rd in Test Management Tools with 10 reviews while Visual Studio Test Professional is ranked 4th in Test Management Tools with 13 reviews. Tricentis qTest is rated 8.4, while Visual Studio Test Professional is rated 8.4. The top reviewer of Tricentis qTest writes "Provides a central point of reference for tracking bugs and failures, who owns the issue and its status". On the other hand, the top reviewer of Visual Studio Test Professional writes "Offers lots of features, including memory analysis and code sharing". Tricentis qTest is most compared with Tricentis Tosca, Micro Focus ALM Quality Center, Cognizant ADPART, Zephyr Enterprise and Inflectra SpiraTest, whereas Visual Studio Test Professional is most compared with TFS, Apache JMeter, Katalon Studio, HCL AppScan and Tricentis Tosca. See our Tricentis qTest vs. Visual Studio Test Professional report.

See our list of best Test Management Tools vendors.

We monitor all Test Management Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.