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."I use the solution for test management."
"I use the product to create test cases and share them with my team and manager."
"The product helps us create test cases and reports."
"The ability to time test runs gives the tester the ability to compare calculated times to actual times it takes for a test case to run."
"Most valuable features are the ease of organizing test cases and a great API for sending results from automated test run results into the database."
"You don't need to follow complex procedures to create a test run, test case, etc."
"The features that I have found most valuable are that there are various test case templates and test artifact maintenance."
"Reliable and stable. It is important that TestRail be up and running 24/7 as we have users around the world using it."
"Works well for test management and is a good testing repository."
"I like the way it structures a project... We're able to put the test cases into qTest or modify something that's already there, so it's a reusable-type of environment. It is very important that we can do that and change our test data as needed..."
"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 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 main thing that really stuck out when we started using this tool, is the linkability of qTest to JIRA, and the traceability of tying JIRA requirement and defects directly with qTest. So when you're executing test cases, if you go to fail it, it automatically links and opens up a JIRA window. You're able to actually write up a ticket and it automatically ties it to the test case itself."
"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 integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"What I found most valuable in Tricentis qTest is that it doesn't require installation. You use it through the URL. It also has an excellent reporting feature."
"With TestRail, the APIs are there, but they may not be able to easily integrate with the Jenkins."
"There are a number of improvements that have been requested. While I don't have a list of these requests available, many can be found on Gurock's forum."
"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 test suite management has room for improvement as well as better reporting."
"TestRail should improve its pricing."
"I have faced some issues with the integration between TestRail and Jira, which haven't been permanently resolved yet."
"It would be nice if they would add an export to Word."
"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."
"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."
"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."
"The Insights reporting engine has a good test-metrics tracking dashboard. The overall intent is good... But the execution is a little bit limited... the results are not consistent. The basic premise and functionality work fine... It is a little clunky with some of the advanced metrics. Some of the colorings are a little unique."
"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."
"I wouldn't say a lot of good things about Insights, but that's primarily because, with so many test cases, it is incredibly slow for us. We generally don't use it because of that."
"Could use additional integration so that there is a testing automation continuum."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
TestRail is ranked 2nd 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.