Tricentis qTest

Score8.5 out of 10

76 Reviews and Ratings

Get a Demo

Tricentis qTest

Get a Demo

What is Tricentis qTest?

Tricentis qTest (formerly QASymphony) provides enterprise-level agile testing tools giving businesses visibility and control needed to ensure application quality in fast-paced development environments. Tricentis and QASymphony merged in summer 2018.

Categories & Use Cases

Media

Customizable analytics and reports can be shared across the organization - additional read license required

Centrally manage automated testing and environments, as well as schedule and or kickoff automated testing with any open source or proprietary tool

qTest allows for true test case sharing across teams and projects to help standardize and scale knowledge and best practices

qTest integrates in real-time with Jira for full traceability to requirements during Agile test and development

Build custom, event-driven workflows with any third-party solution, including ChatOps tools like Slack and Microsoft Teams, to streamline testing and drive collaboration

Tricentis qTest comes with over 60 out-of-the-box metrics, with drag-and-drop capabilities to build custom dashboards

Tricentis qTest includes present dashboards on defects, status, coverage, and velocity, filterable by fields like project and date

Scale and orchestrate automated testing with any tool - Tricentis qTest helps users manage automation hosts, test schedules, and results in one place

1 / 8

Test execution reporting
Comprehensive reporting on which tests have been run and pass/fail
Category average: 8.6
Manage test hosts and schedules
Ease of setup of automated tests and test schedules
Category average: 8.3
Centralized test management
Ability to manages both manual and automated tests from a centralized location
Category average: 8.7

Defect management
Ability to automatically log defects and link them to failed tests, and report defect resolution progress
Category average: 8
Map tests to user stories
Provide visibility into user story test coverage
Category average: 8

Calum Craig View profile

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

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

Other Software Used

Atlassian Jira, Docker, Microsoft 365

Verified User

Consultant in Quality Assurance (10,001+ employees employees)

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.

Return on Investment

Tricentis qTest significantly improved our testing process by increasing visibility, traceability, and collaboration across teams.
It reduced test execution time by centralizing manual and automated test results, helped us catch defects earlier through better test coverage, and standardized testing practices across multiple squads.
we saw fewer escaped defects, faster sprint turnarounds, and more consistent QA reporting, which directly supported our delivery and quality goals."

Other Software Used

Tricentis Tosca, Appium, WebdriverIO

Verified User

Analyst in Information Technology (10,001+ employees employees)

Use Cases and Deployment Scope

We use a Tricentis qTest for both project management and also include defect management end to end and use this for complete test management in the current migration projects

Pros

Test management
Test execution
Defect management
Export test results

Cons

Complete project management with spring board
Kanban support for proj management
Easy integration with automation tools
Simple test execution result and attachments exports so it can be shared across wider audience

Return on Investment

More customisation options
Less report generation/ graph reporting capabilities
Robust test management
Improved user experience with easy navigation
Having bigger button to perform different functions and easy navigation between different tabs- test design, test execution etc.

Alternatives Considered

Rally Software

Other Software Used

IntelliJ IDEA, Perfecto by Perforce, Rally Software

Usability

Verified User

Manager in Quality Assurance (10,001+ employees employees)

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

Return on Investment

Better test standardisation across team definitely, Tricentis qTest had made a highly positive impact on our teams Performance

Alternatives Considered

Capture for Jira and from SmartBear

Verified User

Analyst in Quality Assurance (1001-5000 employees employees)

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

Return on Investment

Integrating qTest in our workflow helped us in 52% reduction in test authoring effort
Overall project management and the time calculation for the quality checking of each project can be managed good in qTest
It provides full tracability of a single project from the requirements to the defects raised it helps our team a lot