We performed a comparison between Panaya Test Dynamix and Tricentis qTest based on real PeerSpot user reviews.
Find out what your peers are saying about OpenText, Microsoft, IDERA and others in Test Management Tools."The most valuable feature is the ability to copy the scenarios and as we do a rollout we can efficiently complete test three and put it somewhere else under a new subsidiary."
"The initial setup was not complex and the product itself is very easy to configure and use."
"Test migration from HPE are done automatically. We can extract our tests from HPE, and they convert it into the Panaya format."
"The solution helps with recording and documentation."
"The test repository to follow the test progress is most valuable because we can easily create and manage a huge number of test scripts. We can copy and paste, replicate, and drag and drop many tests scripts. We can create test scripts en masse. When you have a high volume of tests, the tool is quite useful. It works well when you want to manage a lot of tests, such as you have 1,000 or more test scripts."
"It is easy for business users to use who are not familiar with testing tools."
"Provides better monitoring for testing campaigns and business process testing."
"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."
"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."
"The solution's real-time integration with JIRA is seamless."
"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."
"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."
"They provide options for custom fields or tabs, but customization of workflows would be great."
"The setup of Panaya Recorder is a bit complex. Panaya is a SaaS application, but you need to install some components on your computer. You need to set up your computer to allow Panaya Recorder to work. There are five or six things to do each time you install Panaya for any user. If you miss something, Panaya Recorder doesn't work. So, it is complex to install."
"It would be nice to be able to test offline. What I mean by that is today most of the time things are in the cloud, but sometimes when we are in factories and we do not have network access and we should be able to download a test script into our PCs and do the test offline. Once that is complete we can re-upload it when we have a network connection."
"Support is reactive and in English only."
"Nothing is automatic."
"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 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."
"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."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"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."
"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."
Panaya Test Dynamix is ranked 11th in Test Management Tools with 5 reviews while Tricentis qTest is ranked 6th in Test Management Tools with 16 reviews. Panaya Test Dynamix is rated 8.4, while Tricentis qTest is rated 8.4. The top reviewer of Panaya Test Dynamix writes "More than reliable, with satisfied results for our needs, and excellent testing options". 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". Panaya Test Dynamix is most compared with Tricentis Tosca, Worksoft Certify, Zephyr Enterprise, OpenText ALM / Quality Center and OpenText UFT One, whereas Tricentis qTest is most compared with Tricentis Tosca, OpenText ALM / Quality Center, TestRail, Zephyr Enterprise and SpecFlow.
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.
