Tricentis qTest is a Great Tool for Large QA Organizations
July 18, 2025
Tricentis qTest is a Great Tool for Large QA Organizations

Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Tricentis qTest
At my former company, we used Tricentis qTest as a repository for our manual test cases. That is because we preferred to hand-code our automation test cases using Ruby and Cucumber. When it was time for Regression, we divided up the manual test cases among the entire Engineering organization because there were so many.
Pros
- Tricentis qTest is very good at organizing the test cases with a parent/child relationship using a tree menu.
- The product utilizes modules and folders well to help users find their test cases.
- The product makes it easy to find statistics related to pass/fail.
Cons
- Make it easier to delete old users from the licensing list.
- It is difficult to trace the history of a test when going between projects.
- Allow an admin to easily group tests according to their pass/fail/incomplete status so that they can be followed up on.
- In comparison to other Testing tools, Tricentis qTest was the most expensive.
- We were able to quickly bring international users up to speed on how to use the tool.
- The ability to clone a project rather than create a new one from scratch was a valuable time saver.
- Jira
- Jenkins
We decided not to integrate our on-prem instance of Tricentis qTest with Jira because our company's internal security policy would not allow us to integrate with a shared instance of Jira.
I would say that Tricentis qTest helped quite a bit with testing visibility. It is well designed so that the organizational structure makes it easy to make assessments for risk coverage, compliance (with government standards), and testing processes/practices.
We found that Tricentis qTest and TestRail have some similarities, but the main problem was that we needed to use an existing shared instance of TestRail, and we discovered that there was no easy way to prevent users of other projects from editing or even accidentally deleting our testing content. Another large problem was that the transition of our content from Tricentis qTest to TestRail would not be easy.
Do you think Tricentis qTest delivers good value for the price?
Not sure
Are you happy with Tricentis qTest's feature set?
Yes
Did Tricentis qTest live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Tricentis qTest go as expected?
Yes
Would you buy Tricentis qTest again?
Yes
Comments
Please log in to join the conversation