We performed a comparison between PractiTest and Tricentis qTest based on real PeerSpot user reviews.
Find out what your peers are saying about OpenText, IDERA, Microsoft and others in Test Management Tools."The most valuable feature is the way the libraries are structured so that they were not folder driven."
"UI and UX are pretty easy to understand without much of a problem."
"The solution's real-time integration with JIRA is seamless."
"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..."
"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 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 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."
"Works well for test management and is a good testing repository."
"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."
"It doesn't allow you to connect to multiple different tracking tools."
"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 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."
"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 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."
"Could use additional integration so that there is a testing automation continuum."
Earn 20 points
PractiTest is ranked 15th in Test Management Tools while Tricentis qTest is ranked 6th in Test Management Tools with 16 reviews. PractiTest is rated 8.8, while Tricentis qTest is rated 8.4. The top reviewer of PractiTest writes "Offers one click graphical dashboard reports and advanced customization". On the other hand, 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". PractiTest is most compared with TestRail, Jira, Zephyr Enterprise and Microsoft Azure DevOps, whereas Tricentis qTest is most compared with Tricentis Tosca, OpenText ALM / Quality Center, TestRail, Zephyr Enterprise and TFS.
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.