We performed a comparison between Tricentis qTest and Zephyr Enterprise 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."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."
"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..."
"UI and UX are pretty easy to understand without much of a problem."
"The integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"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."
"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."
"If anyone is looking for a good, lightweight, flexible and agile test management product, I think they would do very well with Zephyr Enterprise."
"The solution does its job well."
"It has many features, but the main things that we need are the test cycles and integration with automation because we have automation for the web and mobile applications. We use it for test case management to run the test cases and get the results. At this moment, it is fulfilling our requirements. We are able to get the test execution report and the test pass and fail report. This summary is delivered to our management."
"We use the solution for test case management."
"It has integration with test automation tools."
"It has 90% of the basic features you need without having to pay a lot of extra money."
"Zephyr Enterprise is a stable solution."
"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 support for Tricentis qTest has room for improvement. The response could be better."
"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."
"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."
"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."
"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."
"The reporting, and the ability to reorganize the test repository, which are a little stifling. There is definitely room for improvement there."
"Security needs improvement to protect customer information better."
"We faced some errors while uploading the test cases."
"The reporting, and the ability to reorganize the test repository, which are a little stifling. There is definitely room for improvement there."
"We have a lot of automation for our products, and we require a utility for its integration with automation. Currently, we have to write this utility ourselves. It would be great if they can provide such a utility."
"We would like support for the agile and behavior-driven development (BDD) approaches."
"Zephyr Enterprise needs to redesign the reporting."
"Creating better default varieties of reporting would make the product much better and more popular."
Tricentis qTest is ranked 6th in Test Management Tools with 3 reviews while Zephyr Enterprise is ranked 4th in Test Management Tools with 3 reviews. Tricentis qTest is rated 8.4, while Zephyr Enterprise is rated 7.8. The top reviewer of Tricentis qTest writes "A very well-manageable tool that offers users with a great UI and UX". On the other hand, the top reviewer of Zephyr Enterprise writes "Useful for test case management, but we faced some errors while uploading the test cases". Tricentis qTest is most compared with Tricentis Tosca, OpenText ALM / Quality Center, TestRail, TFS and Panaya Test Dynamix, whereas Zephyr Enterprise is most compared with TestRail, OpenText ALM / Quality Center, Tricentis Tosca, TFS and Adaptavist Test Management for Jira. See our Tricentis qTest vs. Zephyr Enterprise 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.