Try our new research platform with insights from 80,000+ expert users
Tricentis qTest Logo

Tricentis qTest pros and cons

Vendor: Tricentis
4.1 out of 5

Pros & Cons summary

Buyer's Guide

Get pricing advice, tips, use cases and valuable features from real users of this product.
Get the report

Prominent pros & cons

PROS

Test automation tracking is valuable as it centralizes all test executions, saving time and ensuring comprehensive reporting.
The seamless integration with JIRA enhances traceability and communication, linking test cases directly with JIRA tickets.
Reusability of test cases allows for efficient test management and repeated testing processes, improving time efficiency and quality.
Tricentis qTest provides all test cases in one central repository, enabling easy access and organization.
The reporting feature offers a comprehensive overview of efforts and workload management, aiding in test planning and analysis.

CONS

Insights is incredibly slow for large numbers of test cases, leading users to avoid using it due to performance issues.
The Defects module lacks user-friendliness and robustness, requiring users to manually query the database.
Reporting is complex, requiring multiple queries to obtain necessary data and metrics.
Integration between JIRA and qTest is not user-friendly, with challenges in locating corresponding defects from test results.
Tricentis qTest installation process is command-line oriented, requiring simplification, and user management is limited, as users cannot be deleted, only made inactive.
 

Tricentis qTest Pros review quotes

it_user589632 - PeerSpot reviewer
Sr. Portfolio Manager - Testing at a tech vendor with 201-500 employees
Jun 4, 2017
It is the single source for repository and traceability.
it_user179637 - PeerSpot reviewer
QA Expert with 10,001+ employees
Aug 9, 2017
It's quite easy to use and integrate with any popular tools you might already be using and I would definitely recommend it.
RO
Sr. Manager Quality Assurance at Forcepoint LLC (Formerly Raytheon|Websense)
Oct 24, 2019
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.
Learn what your peers think about Tricentis qTest. Get advice and tips from experienced pros sharing their opinions. Updated: February 2026.
884,933 professionals have used our research since 2012.
reviewer1215417 - PeerSpot reviewer
Senior Director of Quality Engineering at a tech vendor with 1,001-5,000 employees
Oct 24, 2019
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.
JK
Testing Lead Manager at PDC Energy
Oct 28, 2019
qTest helps us compile issues and have one place to look for them. We're not chasing down emails and other sources. So in the grand scheme of things, it does help to resolve issues faster because everyone is working off of the same information in one location.
NM
Quality Assurance Team Lead at Parkview Health
Mar 30, 2020
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...
reviewer1219371 - PeerSpot reviewer
Manager, IT Quality Assurance (EDM/ITSRC/Infrastructure) at a financial services firm with 1,001-5,000 employees
Oct 30, 2019
The solution's real-time integration with JIRA is seamless.
RL
Assistant Vice President, IT Quality Assurance at Guardian Life Insurance
Oct 30, 2019
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.
VS
Product QA Manager at Reflexis Systems
Nov 4, 2019
The integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good.
reviewer1229907 - PeerSpot reviewer
Division Chief with 10,001+ employees
Nov 13, 2019
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.
 

Tricentis qTest Cons review quotes

it_user589632 - PeerSpot reviewer
Sr. Portfolio Manager - Testing at a tech vendor with 201-500 employees
Jun 4, 2017
The graphical reports, API integration with the customized automation test tools and support for the same need to be improved.
it_user179637 - PeerSpot reviewer
QA Expert with 10,001+ employees
Aug 9, 2017
There is some room for improving the documentation for the APIs that they expose.
RO
Sr. Manager Quality Assurance at Forcepoint LLC (Formerly Raytheon|Websense)
Oct 24, 2019
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.
Learn what your peers think about Tricentis qTest. Get advice and tips from experienced pros sharing their opinions. Updated: February 2026.
884,933 professionals have used our research since 2012.
reviewer1215417 - PeerSpot reviewer
Senior Director of Quality Engineering at a tech vendor with 1,001-5,000 employees
Oct 24, 2019
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.
JK
Testing Lead Manager at PDC Energy
Oct 28, 2019
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.
NM
Quality Assurance Team Lead at Parkview Health
Mar 30, 2020
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.
reviewer1219371 - PeerSpot reviewer
Manager, IT Quality Assurance (EDM/ITSRC/Infrastructure) at a financial services firm with 1,001-5,000 employees
Oct 30, 2019
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.
RL
Assistant Vice President, IT Quality Assurance at Guardian Life Insurance
Oct 30, 2019
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.
VS
Product QA Manager at Reflexis Systems
Nov 4, 2019
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.
reviewer1229907 - PeerSpot reviewer
Division Chief with 10,001+ employees
Nov 13, 2019
The installation of the software could be streamlined. We pay for the on-premise support and they help us a lot, but the installation is something which is very command-line oriented.