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."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 solution's real-time integration with JIRA is seamless."
"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."
"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."
"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..."
"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 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 user interface is very friendly."
"I was satisfied with the support given by customer service."
"Customization is the most powerful feature of this product."
"Visual Studio is highly powerful. It's probably the best software development tool on the market."
"The documentation is easy, and it helps us solve our problems."
"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."
"Code testing is the most valuable feature of this solution for developing software."
"Easy to use and easily scalable."
"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."
"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."
"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."
"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."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"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."
"Could use additional integration so that there is a testing automation continuum."
"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 data flow can be improved."
"The solution's deployment is not very easy and should be made easier."
"The solution can improve the startup time."
"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."
"The documentation is limited."
"One of the problems with this solution is you need to be highly technically skilled to operate it, it is not for everyone."
"The documents on the Microsoft website are not very useful, and they ought to make it easier to find answers."
"Sometimes, the product is too complex to use."
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.