We performed a comparison between IBM Rational ALM, OpenText ALM / Quality Center, and TFS based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Atlassian, Nutanix and others in Application Lifecycle Management (ALM) Suites."The integration with Git works well."
"The cataloging is a very valuable feature. For a lot of enterprises, they end up not knowing which applications do specific features. The cataloging helps with this. It's not that verbose, but it still gives you allowances to put in more detail."
"The planning feature is rich with Scrum concepts: Sprint, Sprint retrospective, the rules in the Scrum framework."
"It helped us contain critical things, like source code and several documents, which is very important to us."
"The word emulation and importing is good."
"One of the key advantages of IBM Rational ALM is its workflow capabilities, which enable seamless collaboration between development and production teams and ensure that all stakeholders are aware of the progress and readiness of the solution. Additionally, the solution is good for integration."
"The most valuable feature is the reporting of the CPU usage on the dashboard."
"We have something called the GC (global configuration), which is a unique feature compared to any other competitor we have in the ALM space."
"So the first impression that hits me about HP UFT 14.0 (formerly QTP) is that it seems to be a whole lot faster! But that could be subjective, as I'm running it on a high end gaming system."
"What they do best is test management. That's their strong point."
"The solution is very user-friendly."
"ALM Quality Center is a reliable, consolidated product."
"The most valuable Quality Center feature, I find, is the solution's integration with some of our automation tools. For us, the ability to capture and record and the ease of use from a user perspective, are all key."
"I love linking/associating the requirements to a test case. That's where I get to know my requirement coverage, which helps a lot at a practical level. So, we use the traceability and visibility features a lot. This helps us to understand if there are any requirements not linked to any test case, thus not getting tested at all. That missing link is always very visible, which helps us to create our requirement traceability matrix and maintain it in a dynamic way. Even with changing requirements, we can keep on changing or updating the tool."
"Produces good reports and has a great traceability feature."
"It's basically the way to show the work that we do as QA testers, and to have a historical view of those executions."
"I have found almost all of the features valuable because it integrates well with your Microsoft products. If a client is using the entire Microsoft platform, then TFS would be definitely preferable. It integrates with the digital studio development environment as well."
"Some of the valuable features are version control and the ability to create different collections in terms of segregating the authorization for teams who connect to small projects."
"The most valuable feature of TFS is the central repository, and you can see what changes other developers did from which branch."
"The solution's iteration board is good because you can track all your work with it."
"It has great functionality: work items, backlogs, source code, build releases, and it's easy to use."
"The interface is good with TFS."
"The most valuable feature is integration, particularly if you have a .NET application."
"It is a stable solution."
"I would like to see better reporting features. The out-of-box reporting is - I don't want to say limited - but the focus is on the Scrum and Sprint reports. We need more reporting features regarding the history of the work, tracking it more deeply."
"There is not enough beginner support material in the form of FAQs or simple training to help you get started."
"The product must be more user-friendly."
"The GUI is a little bit outdated."
"The directory designer manager is uncivil. The design manager is clearly really unstable."
"IBM Rational ALM should remove the features not used by the customers and keep this product as lightweight as possible."
"The features should be more intuitive. If I'm looking for something, its location should be easy to locate."
"In the next release, we expect a traceability metrics configuration where we can configure the user stories. We also expect them to improve or simplify the query process."
"The UI is very dated. Most applications these days have a light UI that can be accessed by pretty much any browser; QC still uses a UI which has a look almost the same for the past 20 years."
"I would rate it a 10 if it had the template functionality on the web side, had better interfaces between other applications, so that we didn't have dual data entry or have to set up our own migrations."
"The session timeout time needs to be longer in my opinion."
"There's room for improvement in the requirements traceability with Micro Focus ALM Quality Center. That could use an uplift."
"One drawback is that ALM only launches with the IE browser. It is not supporting the latest in Chrome... It should be launched for all of the latest browsers."
"Currently, what's missing in the solution is the ability for users to see the ongoing scenarios and the status of those scenarios versus the requirements. As for the management tools, they also need to be improved so users can have a better idea of what's going on in just one look, so they can manage testing activities better."
"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."
"There were multiple modules and stuff to the solution so maybe the requirements can map to test scripts. It can't map to test steps. If you've got a process that's set up and you've got multiple test scripts that are in it, each script has to be linked to the requirement and the whole set can't be. If we're doing process-driven testing, it's more difficult to do it at the script level, which is what we're finding from a traceability perspective."
"The overall reports in TFS could improve. Additionally, there should be an easier way to migrate from an older version to a newer one."
"Its pricing could be improved."
"I'm looking for specific options that aren't currently available, such as active status, new status, or what's currently in progress."
"The dashboard needs more enhancements."
"The reporting functionality is something that they should work on."
"In the next release, I would like them to include integration for various projects, similar to what JIRA has, and they could create this feature on the dashboard."
"The solution's server for deployment needs to be improved."
"One of the areas that could be improved is to have an effective full lifecycle management."
More OpenText ALM / Quality Center Pricing and Cost Advice →
