Tricentis qTest Reviews and Ratings

Rating: 8.6 out of 10

Score

8.6 out of 10

Community insights

TrustRadius Insights for Tricentis qTest are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Field Customization: Users have consistently praised the tool for its intuitive field configuration and customization options, which streamline the process of mapping out complex business workflows effectively. The user-friendly interface for customizing fields has been highlighted as a key feature that enhances overall usability.

Cloud Compatibility: Many reviewers have expressed satisfaction with the tool's seamless integration with cloud-based solutions, noting how this capability significantly improves accessibility and flexibility in test management tasks. The ability to leverage cloud resources has been lauded for enhancing collaboration among team members working on testing projects.

Efficient Test Case Management: Customers appreciate the tool's robust functionalities in creating, editing, and organizing test cases efficiently. Its smooth integration with popular platforms like Jira and Selenium for automated script execution has garnered positive feedback from users seeking comprehensive test case management solutions.

Reviews

41 Reviews

Utilising Tricentis qTest capabilities

Rating: 10 out of 10

Incentivized

March 31, 2026

Use Cases and Deployment Scope

We are using Tricentis qTest to maintain test requirements, test cases and track test execution status. It's ability to integrate with Rally is very helpful as we can link defects to the test cases while execution. This is being used from System testing till system integration testing and makes different testing phases easy to manage.

Pros

Providing well defined structure to maintain requirements and test cases
Easy to manage and track test execution cycles
Integration with Rally allows linking defects with test cases

Cons

The different sub sections during test execution , with option to create test cycle etc, sometimes feel redundant. Every team used it differently. Is there can be a standard structure during test execution, that will help

Likelihood to Recommend

Tricentis qTest is mostly we'll suited as it's helping our team to manage test executions and maintain test repositories in an efficient way

Verified User

Manager in Quality Assurance (10,001+ employees)

Vetted Review

5 years of experience

Tricentis qTest is a decent test tool

Rating: 7 out of 10

Incentivized

December 15, 2025

Use Cases and Deployment Scope

We use Tricentis qTest as our main testing tool - covering both manual and automated tests. It is connected to our corporate Jira set up so we can easily import tickets as requirements for test cases and build up from there.

To be perfectly honest, I view test tools as a necessary evil and with that caveat I would say that Tricentis qTest is one of the better ones I have used.

It keeps things fairly simple: we create test cycles, spin off execution runs (repeated if needed) and do our testing. I can raise defects straight from the execution window and these again are integrated with Jira which makes life easier, no need for duplication of effort. We attach all our test evidence and we're done.

I recently coordinated the regression testing for our mobile app release and the Tricentis qTest dashboard gave me a simple visual update on progress I could share with our stakeholders.

Pros

Jira integration
Raising defects
Creating test execution runs

Cons

I feel the UI is kind of clunky
Finding requirements can be challenging

Likelihood to Recommend

Tricentis qTest is ideal for tracking manual test effort. I'm not convinced a test tool like it is really necessary for automated testing. It works well to coordinate a test team as tests can be assigned individually.

I find creating test scripts a bit unwieldy and frequently end up with multiple Tricentis qTest windows open, copying and pasting.

Calum Craig

Senior Test Engineer in Information Technology at Tesco Bank (501-1000 employees)

Vetted Review

3 years of experience

View profile

Tricentis qTest Review

Rating: 10 out of 10

Incentivized

October 15, 2025

Use Cases and Deployment Scope

We use qTest to manage test cases, link them to user stories, and track defects across manual and automated tests. It helps us improve traceability, streamline test execution, and ensure faster feedback during sprints. Our use spans across QA teams for functional, regression, and integration testing.

Pros

Organizes test cases in a clear, hierarchical structure by release, module, or feature
Seamlessly integrates with Jira, allowing automatic linking of test cases to stories, bugs, and requirements
Allows batch execution of tests across environments and releases
Offers real-time status dashboards, so QA leads and PMs can monitor progress and defects

Cons

The UI can feel outdated at times, requiring too many clicks to perform simple actions like cloning test cases or switching between modules.
Large projects with thousands of test cases can cause sluggish load times, especially in the Test Design and Execution tabs.
Built-in reports are helpful, but customizing dashboards often requires external BI tools or API scripting.

Likelihood to Recommend

Tricentis qTest integrates seamlessly with Jira, making it ideal for teams that manage user stories and defects in Jira while keeping test cases and execution in qTest. When paired with automation tools like Tosca, Selenium, or WebdriverIO, qTest is excellent for aggregating both manual and automated test results in one place.

Verified User

Consultant in Quality Assurance (10,001+ employees)

Vetted Review

2 years of experience

How as a fresher qTest helped in testing phase of a software.

Rating: 10 out of 10

Incentivized

October 2, 2025

Use Cases and Deployment Scope

qTest is the primary testing tool in our Org. We primarily use this for salesforce and related business applications. It helps us to follow QA's agile process and helps us in delivering high quality testing. It also helps Business Analysts and many other teams to collaborate and look into what our team (QA) is actually working on and what all test cases we are drafting and how are we testing them.

Business Problems addressed: It mainly address the huge problem each company faces which is - 'centralized test management'. Currently we are not facing this issue as we integrated qTest in our daily workflow and it helps us a lot in our QA work routine.

The other problem is other teams (outside QA) if they want to know the type of quality we are providing they need not to explicitly ask us as qTest contains all the Test cases that we run as part of a JIRA and they can refer them if they want to address or replicate any scenario they we as a QA team tested.

Pros

As a fresher, when I started using qTest it was very handy and easy to understand.
It helps us trace the test cases that are used to test the quality in a single location
The main thing is its integration with JIRA as soon as we create a ticket we would be getting all the requirements in the qTest so it became easy for me

Cons

Better integration with JIRA as sometimes I faced the requirements not getting filled automatically in qTest
I also noticed some times when I pause the session also it records where ever I press the mouse so little improvement on that side
Some glitches while starting a session for testing

Likelihood to Recommend

qTest helps the org's whcih are mainly focused for centralized test management tool for their QA team as it provides a great experience to them as a starter tool for testing. It also helps other teams in your org's to collaborate more efficiently for re-visiting some testing scenarios while facing any issues after a quality check.

Verified User

Analyst in Quality Assurance (1001-5000 employees)

Vetted Review

1 year of experience

qTest is for making QA life easy by bringing all STLC entities under one roof

Rating: 9 out of 10

Incentivized

August 7, 2025

Use Cases and Deployment Scope

Earlier our test case for execution were scattered across many g-docs & the purpose of Tricentis qTest was to bring all STLC i.e. Test authoring, Test management, test execution & reporting under 1 tool. Tricentis qTest helped us to get all this together & track effectively. Especially when we were not using qTest we were losing our past data of "proof of testing" now it has become easy for us to focus on just execution & authoring rest toll will handle for us & drive us thru needy numbers

Pros

Proof of testing maintenance thru "web explorer option"
Execution report is easily derivable
Authoring & Execution tracking
Ease of maintainance

Cons

At times server errror cost us half a day of work
"Web explorer" sometimes goes for toss & collection of test proof becomes hard
when there are bulk actions are performed we see glitch (rare-case)

Likelihood to Recommend

After we started using Tricentis qTest we experienced that "proof of testing" recording thru "web explorer" is more appropriate & flexible feature that makes tester life easy

When it comes to less appropriate scenario is, i personally felt there are very less but mapping between test plan & requirement is not needed when we map between TC's & Requirement

Navaneeth T

QA Manager in Quality Assurance at CONFLUENT (1001-5000 employees)

Vetted Review

Tricentis qTest is a Great Tool for Large QA Organizations

Rating: 8 out of 10

Incentivized

July 18, 2025

Use Cases and Deployment Scope

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.

Likelihood to Recommend

In our organization, Tricentis qTest was well suited for storing our manual test cases, but not as much for our automated test cases. We would create dummy stories for the automated tests so that it appeared to observers that work was actually done in those areas.

Verified User

Manager in Quality Assurance (10,001+ employees)

Vetted Review

12 years of experience

qTest for Test Management

Rating: 8 out of 10

Incentivized

July 18, 2025

Use Cases and Deployment Scope

We use Tricentis qTest to help clients standardize and optimize test planning and repositories. We also use it with clients for manual and exploratory testing since not everything can be automated. As with anything, there's a learning curve. But leveraging qTest to store test scenarios in a clean way, also linking everything back to requirements provides traceability from start to finish. It also doesn't depend what automation platform we're using, qTest integrates well through qTest Pulse via API and webhooks. This is one of the elite commercial/enterprise grade test management platforms to exist.

Pros

Cleanly organized repository structure for team to standardize to
Gives me real time, historical, and future visibility as to the state of testing (results, in progress, planned - then all linked to requirements)
Deep integration with a variety of automation tools and requirements management tooling

Cons

Modular features create a feeling of overload and unnecessary complexity for newer users
Reporting directly in qTest is lacking compared to BI tools (but it integrates directly to circumvent this)
Not a strong defect manager

Likelihood to Recommend

It entirely depends on the goals of your organization. The more complex, large scale, feature needy environments, Tricentis qTest thrives in. If you need simple and small, Tricentis qTest could be overkill. Best when deployed across multiple teams doing a multitude of activities, so management can best measure and allocate. Users need to dedicate time to training, but when enabled fully, qTest can work wonders.

Verified User

Partner in Professional Services (51-200 employees)

Vetted Review

Reseller

3 years of experience

Tricentis qTest Great Investment

Rating: 8 out of 10

Incentivized

April 22, 2025

Use Cases and Deployment Scope

We use qTest to track our regression and functional tests. We also use the qTest Explorer to record all of tests to have great reproduction steps.

Pros

Importing from JIRA
Screen recording
Test Case management

Cons

Graphic interface
Speed when moving through the components
Needs a dark mode

Likelihood to Recommend

Verified User

Team Lead in Quality Assurance (11-50 employees)

Vetted Review

5 years of experience

Tricentis qTest Enterprise Testing Powerhouse

Rating: 9 out of 10

Incentivized

April 11, 2025

Use Cases and Deployment Scope

<span style="font-size: 1rem;">We use Tricentis qTest to organize and track our testing work. It helps us create test cases, run tests, log defects, and generate reports—all in one place. It connects with Jira and our CI/CD pipeline, making it easy to sync with development. </span><div>

</div><div>Before qTest, we struggled with scattered test data and slow reporting. Now, we have clear dashboards to track progress and make better decisions. It works for both manual and automated testing, saving us time. </div><div>Our team uses it for functional, regression, and API testing. It fits well with Agile and DevOps, helping us deliver faster.</div>

Pros

Test Case Management & Reusability
Real-Time Dashboards & Reporting

Cons

Steeper Learning Curve

Likelihood to Recommend

Best Case Scenario 1. Large-Scale Enterprise Testing Example: qTest’s requirement traceability and audit trails ensured compliance with strict regulatory standards 2. Agile/DevOps Teams with Jira Example:In a CI/CD pipeline, qTest’s Jira sync automated defect logging. Developers fixed bugs faster because tickets included linked test steps and screenshots. 3. Manual Regression Testing Example: Versioned test cases and bulk editing streamline repetitive workflows.

Less Appropriate Scenarios 1. Small Teams with Simple Projects Example: Heavyweight for lightweight needs 2. Mobile-First Testing Example: Lacks native mobile testing features (e.g., real-device support).

Verified User

Team Lead in Information Technology (10,001+ employees)

Vetted Review

2 years of experience

A Must tool for your testing needs

Rating: 9 out of 10

Incentivized

April 11, 2025

Pros

Test Execution
Requirement mapping
Test Design
Jira Integration

Cons

Creating custom dashboard
Having option to create reusable components

Likelihood to Recommend

It’s best suited for overall test management in your Software testing lifecycle. It’s great for creating test repository and mapped to requirements. It can be very well used by testers , managers to keep track of work at one place.

It’s less suited for creating automation script, tosca is better option for such requirements

Verified User

Team Lead in Professional Services (501-1000 employees)

Vetted Review

2 years of experience

Loading Reviews List....

Home
,
Test Management
,
Tricentis qTest
,
Reviews and Ratings

How as a fresher qTest helped in testing phase of a software.

Rating: 10 out of 10

Incentivized

October 2, 2025

Use Cases and Deployment Scope

Pros

As a fresher, when I started using qTest it was very handy and easy to understand.
It helps us trace the test cases that are used to test the quality in a single location
The main thing is its integration with JIRA as soon as we create a ticket we would be getting all the requirements in the qTest so it became easy for me

Cons

Better integration with JIRA as sometimes I faced the requirements not getting filled automatically in qTest
I also noticed some times when I pause the session also it records where ever I press the mouse so little improvement on that side
Some glitches while starting a session for testing

Likelihood to Recommend

Verified User

Analyst in Quality Assurance (1001-5000 employees)

Vetted Review

1 year of experience