We performed a comparison between Helix ALM, OpenText ALM / Quality Center, and TFS 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 features of Helix ALM are traceability and flexibility."
"The tool offers high stability."
"Helix ALM enables users to build, make efficient and effective decisions, and use least-cost methods for maximum benefit, as fast as possible. They allow you to see and visualize your configuration."
"This solution is open and very easy to integrate. The interface is good too."
"Reporting was the main thing because, at my level, I was looking for a picture of exactly what the coverage was, which areas were tested, and where the gaps were. The reporting also allowed me to see test planning and test cases across the landscape."
"I love to use this solution with single projects. It has helped our productivity. With the metrics that I receive, I can put them onto the management model so I can see them there. It has reduced our time for project management and controls by 20 percent."
"Business process management is the most valuable feature of the solution."
"Being able to manage tests as this is something very difficult to find in other products."
"Having the links maintained within the tool is a huge boon to reporting requirements, tests, and defects."
"The integration with UFT is nice."
"Defect management is very good."
"User alerts are very helpful for knowing when work is required."
"Good branching and labelling features."
"The interface is easy to navigate."
"The most valuable feature of TFS is the central repository, and you can see what changes other developers did from which branch."
"Work item management integration with source control."
"It has great functionality: work items, backlogs, source code, build releases, and it's easy to use."
"The work item feature is most valuable. It allows us to store all product requirements. We can also link the test cases to those requirements so that we know which feature has already been tested, and which one is waiting for testing. We can also couple the code reviews, unit tests, and automated tests into these requirements. It is reliable. It has all the features and good performance. It also has reporting tools or analysis tools."
"TFS is very user-friendly."
"It would be great to see Perforce's strategy is for implementing intelligence into the process via AI or ML. It's not clearly defined, at least not to my knowledge."
"The accountability and the equivalent to using, acting, editing, working with Word, and also importing and exporting from Word needs improvement."
"Helix ALM should be able to integrate with other systems better. Helix ALM should also have an easier user interface, and the solution needs to have drag-and-drop tools included in it."
"I'm looking at more towards something more from a DevOps perspective. For example, how to pull the DevOps ecosystem into the Micro Focus ALM."
"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."
"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."
"There needs to be improvement in the requirement samples. At the moment, they are very basic."
"The product is good, it's great, but when compared to other products with the latest methodologies, or when rating it as a software development tool, then I'll have to rate it with a lower score because there's a lot of other great tools where you can interconnect them, use them, scale them, and leverage. It all depends on the cost."
"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 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."
"There's room for improvement on the reporting side of things and the scheduling, in general, is a bit clunky."
"TFS should allow more integration with different platforms."
"The reporting functionality is something that they should work on."
"They should have design patterns in TFS for the development team, and design patterns for the QA."
"The tool needs improvement in stability."
"I'm looking for specific options that aren't currently available, such as active status, new status, or what's currently in progress."
"Sometimes we feel that it need more CPU, and RAMs on TFS server, either we implemented the hardware with the product minimum requirements."
"TFS is scalable with different Microsoft tools for test management but it is not scalable with other third-party tools."
"There are many things that I cannot do, and I have a lot of bugs."
More OpenText ALM / Quality Center Pricing and Cost Advice →
