We performed a comparison between Tricentis qTest and Zeenyx AscentialTest based on real PeerSpot user reviews.
Find out what your peers are saying about OpenText, Microsoft, IDERA and others in Test Management Tools."The solution's real-time integration with JIRA is seamless."
"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."
"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."
"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..."
"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."
"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."
"Works well for test management and is a good testing repository."
"It’s been really easy to automate the same application TestComplete struggled with. I have been able to automate two of our key applications in just a few months. I haven’t even taken their training."
"AscentialTest's object recognition in snapshots is a robust feature that goes beyond standard elements, even accurately identifying objects within Datawindows."
"The most valuable feature of AscentialTest for us is that it fully supports PowerBuilder."
"If you use the PowerBuilder application, do choose AscentialTest without thinking twice."
"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."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"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."
"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."
"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."
"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 would like to see an improvement in the User Interface."
"Streamlining the retrieval of results from individual test set runs would be beneficial."
"The only thing I can't wait for is for Zeenyx to add automating Mobile apps."
"Classes are not as object-oriented as I would like, but I am a programmer and not QA so I expect a lot."
Earn 20 points
Tricentis qTest is ranked 6th in Test Management Tools with 16 reviews while Zeenyx AscentialTest is ranked 25th in Test Management Tools with 13 reviews. Tricentis qTest is rated 8.4, while Zeenyx AscentialTest is rated 9.4. 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 Zeenyx AscentialTest writes "Robust automation with reusable steps and seamless integration". Tricentis qTest is most compared with Tricentis Tosca, OpenText ALM / Quality Center, TestRail, Zephyr Enterprise and TFS, whereas Zeenyx AscentialTest is most compared with Tricentis Tosca, SmartBear TestComplete and Selenium HQ.
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.