We performed a comparison between Tricentis qTest and Visual Studio Test Professional based on real PeerSpot user reviews.
Find out in this report how the two Test Management Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Works well for test management and is a good testing repository."
"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."
"UI and UX are pretty easy to understand without much of a problem."
"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."
"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 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 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 integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"Visual Studio Test Professional is a scalable solution."
"The most valuable features are tools like IntelliSense and ReSharper."
"The interface is easy to use."
"The tool has highly detailed debugging features."
"One of the best documentation in the world."
"Visual Studio Test Pro is super helpful for my Microsoft app work."
"It's great for the development of .NET."
"The debugging feature is valuable."
"The support for Tricentis qTest has room for improvement. The response could be better."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"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."
"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."
"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."
"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."
"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."
"Visual Studio Test Professional could improve by having better integration with external databases."
"Sometimes, the solution hangs, so its performance could be improved."
"The tool crashes and has high memory consumption."
"The data flow can be improved."
"The documents on the Microsoft website are not very useful, and they ought to make it easier to find answers."
"Enhancing the support for web application testing and load performance would be an improvement."
"There are too many features with the product and I would like there to be less."
"The service right now is far too expensive. You need to pay per user."
More Visual Studio Test Professional Pricing and Cost Advice →
Tricentis qTest is ranked 6th in Test Management Tools with 16 reviews while Visual Studio Test Professional is ranked 5th in Test Management Tools with 48 reviews. Tricentis qTest is rated 8.4, while Visual Studio Test Professional is rated 8.6. The top reviewer of Tricentis qTest writes "Puts all our test cases in one location where everyone can see them. qTest also allows the segregation of different types of Testing". On the other hand, the top reviewer of Visual Studio Test Professional writes "Customization is a key feature as is the ability to integrate with third-party services ". Tricentis qTest is most compared with Tricentis Tosca, OpenText ALM / Quality Center, TestRail, Zephyr Enterprise and Adaptavist Test Management for Jira, whereas Visual Studio Test Professional is most compared with TFS, Apache JMeter, Tricentis NeoLoad, SmartBear TestComplete and Katalon Studio. 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.