We performed a comparison between Helix ALM, PractiTest, 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."
"The most valuable feature is the way the libraries are structured so that they were not folder driven."
"TFS’s test management capability without the expensive licensing has large gaps. Users will be unable to access performance testing and coded UI testing capabilities."
"The most valuable features of TFS are bug reporting and its high performance."
"The most valuable features of TFS are the test plans. We can reproduce reusable test plans in test automation. We have a lot of queries and this feature is very useful."
"Since it is a robust solution, I face no performance issues. Also, considering how well the implementation process of the solution was carried out, we never faced any issues while using the solution."
"The most valuable feature is integration, particularly if you have a .NET application."
"It is easy to push our changes from quality to pre-prod and prod."
"I feel that the test plan and test tools are more manageable in TFS."
"The solution's iteration board is good because you can track all your work with it."
"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."
"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."
"It doesn't allow you to connect to multiple different tracking tools."
"They have room for improvement in merging the source code changes for multiple developers across files. It is very good at highlighting the changes that the source code automatically does not know how to handle, but it's not very good at reporting the ones that it did automatically. There are times when we have source code that gets merged, and we lose the changes that we expected to happen. It can get a little confusing at times. They can just do a little bit better on the merging of changes for multiple developers."
"The reporting functionality is something that they should work on."
"The interface can be improved and made more user-friendly."
"It has been really dated. When you start to work more in an agile environment, it is not really that flexible. They tried to replicate the look and feel of Jira, but it is not quite there. It was nice to use in the past, but it is not as flexible now with the changing development environments and methodologies."
"The solution is stable but could improve."
"I would like to see TFS improve its web interface as there are some limitations with IDs and the integration behind it and with open-source tools like VS Code."
"The dashboard needs more enhancements."
"Overall, I think it would be useful to have something similar where Microsoft comes up with supporting concepts of scaling Agile in TFS so that clients don't have to look for a separate tool."
Earn 20 points