We performed a comparison between TestRail and TFS 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 solution is very stable. We've never had any issues with it."
"I use the product to create test cases and share them with my team and manager."
"The most valuable features are the flexibility, ease of use for writing new test cases, the test plans, and the composition."
"The integration with Jira and the ability for extra configurations are the most valuable features."
"The feature that I have found most valuable is the dashboard."
"The API to support integration of the homemade automated testing tool."
"From a testing perspective, the management is awesome. I am able to do testing and then add the reporting and the evidence. It is fair in terms of the price that you're paying. You get what you're paying for."
"I use the solution for test management."
"The most valuable features of TFS are bug reporting and its high performance."
"TFS is very user-friendly."
"It is a stable solution."
"The initial setup is fairly easy."
"Basically, the capacity to construct various products is something I find handy."
"The most valuable features are related to source code management. Using TFS for source code management and being able to branch and have multiple developers work on the same projects is valuable. We can also branch and merge code back together."
"The most valuable features are the dashboard and task-selection capability."
"The most valuable feature of TFS is integration."
"TestRail by Gurock could improve by adding a defect management module tool. It would add a lot of value if I want to install it and I don't have Jira or an isolating team. For example, if I am providing a service it's separated from the development team, it then would be better to have defect management included with the test management. However, as it is now I need to be integrated with Jira or another defect management tool to complete the testing process."
"With TestRail, the APIs are there, but they may not be able to easily integrate with the Jenkins."
"I have faced some issues with the integration between TestRail and Jira, which haven't been permanently resolved yet."
"I do see room for lots of improvement in it. In terms of usability, duplication with test cases and constant creation of projects isn't easy. There is also too much API integration into automation tools, which is not there in ALM with UFT. Instead of setting it up as a project and using it, we set it up as a system for usability. It also lacks in the traceability aspect. For traceability, you need to use the JIRA plugin and drag traceability on JIRA, but the functionality is still quite limited. The biggest gap is mainframe testing. It would be good if I could start with mainframe testing. Manual granting of access is another issue. There is no API that I could use with another system where it is automated. There is an API for loading somebody to a project but not for adding to the application."
"TestRail should improve its pricing."
"The platform needs improvement regarding performance and creating links."
"It would be useful if it had its own issue management system. At the moment, it's purely a test management tool and you have to link to a defect management tool, like JIRA. It would be useful if there was an option to use its own defect management tool so that it's integrated and not two separate tools."
"It would be nice if they would add an export to Word."
"The user interface could improve and test management was not useful in TFS."
"As an end-user, I expect the solution's performance to be faster while staying as stable as possible."
"There are many things that I cannot do, and I have a lot of bugs."
"One of the areas that could be improved is to have an effective full lifecycle management."
"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."
"More options could be provided from the perspective of requirements management, which would help product owners to use the tool effectively."
"The interface can be improved and made more user-friendly."
"The price could be cheaper."
TestRail is ranked 2nd in Test Management Tools with 21 reviews while TFS is ranked 3rd in Test Management Tools with 93 reviews. TestRail is rated 8.0, while TFS is rated 8.0. The top reviewer of TestRail writes "A tool that provides effective test management and real-time reporting capabilities". On the other hand, the top reviewer of TFS writes "It is helpful for scheduled releases and enforcing rules, but it should be better at merging changes for multiple developers and retaining the historical information". TestRail is most compared with Zephyr Enterprise, Tricentis qTest, Tricentis Tosca, Sealights and PractiTest, whereas TFS is most compared with Microsoft Azure DevOps, Jira, Rally Software, Visual Studio Test Professional and Zephyr Enterprise. See our TFS vs. TestRail 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.
