We performed a comparison between OpenText ALM / Quality Center and Tricentis qTest 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 the ST Add-In. It's a Microsoft add-in that makes it much easier to upload test cases into Quality Center."
"Templates: Allows us to standardize fields, workflows throughout hundreds of HPE ALM projects."
"It's easy to create defects and easy to sync them up with a developer. Immediately, once created, it will trigger an email to the developer and we'll start a conversation with the developer regarding the requirements that have not been matched."
"The solution's support team was always there to help."
"By using QC we broke down silos (of teams), improved the organization of our tests, have a much better view of the testing status, and became much quicker in providing test results with document generation."
"It's user friendly, scalable, and very stable and strong. It's cooperative, meaning that I can assess the test to check it and follow the flow of defects, and the developers and the business can use this tool to follow the test process."
"It has a brand new look and feel. It comes with a new dashboard that looks nice, and you can see exactly what you have been working with."
"The stability is very good."
"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..."
"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."
"UI and UX are pretty easy to understand without much of a problem."
"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."
"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."
"Works well for test management and is a good testing repository."
"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 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."
"It can be quite clunky, and it can easily be configured badly, which I've seen in a couple of places. If it is configured badly, it can be very hard to use. It is not so easy to integrate with other products. I've not used Micro Focus in a proper CI/CD pipeline, and I haven't managed to get that working because that has not been my focus. So, I find it hard. I've often lost the information because it had committed badly. It doesn't commit very well sometimes, but that might have to do with the sites that I was working at and the way they had configured it."
"ALM requires that you install client side components. If your organization does not allow admin rights on your local machine, this means you will need someone to run the installation for you with admin rights. This client side install is also limited to Internet Explorer and does not support any other browsers."
"The UFT tests don't work very well and it seems to depend on things as simple as the screen resolution on a machine that I've moved to."
"ALM only works on Internet Explorer. It doesn't work on any other browser. In my opinion, Internet Explorer is generally a bit slower. I would like to see it work on Chrome or on other browsers."
"Requirements management could be improved as the use is very limited. E.g., they have always stated that, "You can monitor and create requirements," but it has its limitations. That's why companies will choose another requirements management solution and import data from that source system into Quality Center. Micro Focus has also invested in an adapter between Dimensions RM and ALM via Micro Focus Connect. However, I see room for improvements in this rather outdated tool. I feel what Micro Focus did is say, "Our strategy is not to improve these parts within the tool itself, but search for supported integrations within our own tool set." This has not been helpful."
"The QA needs improvement."
"We are looking for more automation capabilities."
"It's not intuitive in that way, which has always been a problem, especially with business users."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from 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."
"The support for Tricentis qTest has room for improvement. The response could be better."
"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 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."
"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."
"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."
More OpenText ALM / Quality Center Pricing and Cost Advice →
OpenText ALM / Quality Center is ranked 1st in Test Management Tools with 197 reviews while Tricentis qTest is ranked 6th in Test Management Tools with 16 reviews. OpenText ALM / Quality Center is rated 8.0, while Tricentis qTest is rated 8.4. The top reviewer of OpenText ALM / Quality Center writes "Offers features for higher-end traceability and integration with different tools but lacks in scalability ". 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". OpenText ALM / Quality Center is most compared with Microsoft Azure DevOps, OpenText ALM Octane, Jira, Zephyr Enterprise and OpenText UFT One, whereas Tricentis qTest is most compared with Tricentis Tosca, TestRail, Zephyr Enterprise, TFS and Panaya Test Dynamix. See our OpenText ALM / Quality Center vs. Tricentis qTest 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.
