We performed a comparison between TestRail 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 product helps us create test cases and reports."
"The most valuable features are the flexibility, ease of use for writing new test cases, the test plans, and the composition."
"I haven't faced any stability issues using the solution. Stability-wise, I rate the solution a ten out of ten."
"I use the product to create test cases and share them with my team and manager."
"The integration with Jira and the ability for extra configurations are the most valuable features."
"The features that I have found most valuable are that there are various test case templates and test artifact maintenance."
"The most valuable features are the reporting in the dashboard and the general way in which we can create test runs is helpful."
"I use the solution for test management."
"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."
"I found the reporting aspect to be the most valuable as it provided a comprehensive overview of the efforts needed and the workload for individual tests."
"The most valuable feature is reusing test cases. We can put in a set of test cases for an application and, every time we deploy it, we are able to rerun those tests very easily. It saves us time and improves quality as well."
"The most important feature which I like in qTest manager is the user-friendliness, especially the tabs. Since I'm the admin, I use the configuration field settings and allocate the use cases to the different QA people. It is not difficult, as a QA person, for me to understand what is happening behind the scenes."
"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 integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"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."
"The solution's real-time integration with JIRA is seamless."
"Reporting could be more flexible regarding repeating reports."
"TestRail should improve its pricing."
"It would be nice to have a description section when creating the test scenario itself so I can indicate what the configuration should be."
"The reports should be more user-friendly."
"With TestRail, the APIs are there, but they may not be able to easily integrate with the Jenkins."
"The platform needs improvement regarding performance and creating links."
"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."
"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."
"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."
"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."
"I would really love to find a way to get the results, into qTest Manager, of Jenkins' executing my Selenium scripts, so that when I look at everything I can look at the whole rather than the parts. Right now, I can only see what happens manually. Automation-wise, we track it in bulk, as opposed to the discrete test cases that are performed. So that connection point would be really interesting for me."
"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."
"The support for Tricentis qTest has room for improvement. The response could be better."
TestRail is ranked 3rd in Test Management Tools with 21 reviews while Tricentis qTest is ranked 6th in Test Management Tools with 16 reviews. TestRail is rated 8.0, while Tricentis qTest is rated 8.4. 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 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". TestRail is most compared with Zephyr Enterprise, TFS, Tricentis Tosca, Sealights and PractiTest, whereas Tricentis qTest is most compared with Tricentis Tosca, OpenText ALM / Quality Center, Zephyr Enterprise, TFS and Panaya Test Dynamix. See our TestRail 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.
