Tricentis qTest

Tricentis qTest
Formerly QASymphony

Customer Verified
Score 5.1 out of 10
Tricentis qTest

Overview

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.
Read more

Recent Reviews

Tricentis qTest review

1 out of 10
July 01, 2022
We have 30-40 daily users creating and running test cases. We use Tricentis qTest to demonstrate proof of test execution with objective …
Continue reading
Read all reviews

How Tricentis qTest Differs From Its Competitors

Visibility and Analytics

With Tricentis qTest we are able to provide visibility of our test execution at the end of each sprint for release sign-off by various stakeholders. By providing this visibility it creates increased confidence into the quality of the release.
Continue reading

Visibility and Analytics

Again, we've only been using Tricentis qTest Explorer because we found the test management features it provides too cumbersome for our needs. Tools should support a team's existing workflow, not dictate the tool's own workflow, which is the impression I got when we evaluated the other features.
Continue reading

Visibility and Analytics

Because of the challenges we experienced set up the tool, we weren't able to use the tool extensively enough to get an accurate feel for this. Even before we were fully established with the tool, we were regularly receiving emails from Tricentis qTest (incl. directly from our relationship manager) …
Continue reading

Visibility and Analytics

I wish I could say that qTest improved visibility into our coverage, but the reporting aspects of qTest have changed so often and so drastically over our time using it that we have never really gotten a strong feeling for how much this visibility has increased. What's more, our internal audit team …
Continue reading

Visibility and Analytics

The ability to view aggregate regression testing efforts, including both our manual and automated testing approaches, is improved using qTest. Visibility into the overall progress of said efforts also allows for the necessary discussions to take place in order to reduce delivery delays. For …
Continue reading

Visibility and Analytics

qTest has greatly approved our Quality Management processes and provides visibility to our Business and Technology stakeholders into our Testing activities. Prior to qTest, we did not have standard methods to document and store our Test Cases between our multiple Product teams. Also, it allows QA …
Continue reading

Popular Features

View all 5 features
  • Centralized test management (10)
    8.2
    82%
  • Map tests to user stories (7)
    7.0
    70%
  • Test execution reporting (9)
    6.4
    64%
  • Manage test hosts and schedules (6)
    5.3
    53%

Reviewer Pros & Cons

View all pros & cons

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Tricentis qTest, and make your voice heard!

Return to navigation

Pricing

View all pricing

Entry-level set up fee?

  • Setup fee optional
For the latest information on pricing, visithttps://www.tricentis.com/products/unif…

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Starting price (does not include set up fee)

  • $1,000 per year per user
Return to navigation

Features

Test Management

Test management tools are used to manage the entire testing process comprehensively, removing the need for multiple software tools to manage individual steps in the testing process

6.7Avg 7.9
Return to navigation

Product Details

What is Tricentis qTest?

Tricentis qTest is a scalable test management solution that integrates with planning, testing, and DevOps tools, like Jira, Selenium, and Jenkins, giving teams a complete, unified view of testing throughout the software development cycle. It supports Agile, waterfall, or any hybrid methodology, allowing QA and development teams to approach testing strategically and collaboratively, and  to release higher quality software faster.

Tricentis qTest Features

Test Management Features

  • Supported: Centralized test management
  • Supported: Manage test hosts and schedules
  • Supported: Map tests to user stories
  • Supported: Test execution reporting
  • Supported: Defect management

Tricentis qTest Screenshots

Screenshot of Powerful, customizable analytics and reports can be shared easily across the organization - additional read license requiredScreenshot of Centrally manage automated testing and environments, as well as schedule and or kickoff automated testing with any open source or proprietary toolScreenshot of qTest allows for true test case sharing across teams and projects to help standardize and scale knowledge and best practicesScreenshot of qTest integrates seamlessly in real-time with Jira for full traceability to requirements during Agile test and developmentScreenshot of Build custom, event-driven workflows with any third-party solution, including ChatOps tools like Slack and Microsoft Teams, to streamline testing and drive collaborationScreenshot of Tricentis qTest comes with over 60 out-of-the-box metrics, with drag-and-drop capabilities to build custom dashboardsScreenshot of Tricentis qTest includes present dashboards on defects, status, coverage, and velocity, filterable by fields like project and dateScreenshot of Scale and orchestrate automated testing with any tool - Tricentis qTest helps you manage automation hosts, test schedules, and results in one place

Tricentis qTest Videos

Tricentis qTest Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating SystemsWindows, Linux
Mobile ApplicationNo
Supported CountriesGlobal
Supported LanguagesEnglish

Frequently Asked Questions

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.

Tricentis qTest starts at $1000.

Micro Focus ALM / Quality Center, QMetry Test Management, and Zephyr Enterprise are common alternatives for Tricentis qTest.

Reviewers rate Centralized test management highest, with a score of 8.2.

The most common users of Tricentis qTest are from Mid-sized Companies (51-1,000 employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews

(1-12 of 12)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Centralizing and organizing our test cases as well and as I and my QA Managers/Leads now have oversight into test case coverage of the user stories as well as test execution progress. We are also able to link each test case back to the product requirements and report how many test cases have been automated.
  • Enterprise Test Case Management features
  • QA process reporting and visibility
  • Allows us to scale our test practice
  • Easy to use and nicely integrates into our SDLC
  • Better integration with our Test Automation suites
  • Ability to customize our test execution reporting
  • User experience could be improved
Tricentis qTest is suited for our QA teams who are technical however not very well suited for the Business Testers who are used to working with Jira to enter test cases and manage their testing. A simplified UI would be better suited for these users.
Score 1 out of 10
Vetted Review
Verified User
We have 30-40 daily users creating and running test cases. We use Tricentis qTest to demonstrate proof of test execution with objective evidence.
  • Basic Test Case design
  • Tracking Test runs
  • Traceability
  • Poor reliability
  • Poor support and issue resolution
  • unable to track upload/deletion of attachments
  • Frequent unexplained downtimes
Poor support and follow-up on resolution of issues.
Score 8 out of 10
Vetted Review
Verified User
We utilize Tricentis qTest as a manual test case management solution and integrate it with Jenkins to also include automated testing.
  • Provide a single solution for test case management
  • Provide a methodology of reporting test results
  • Integrate with Jenkins to facilitate automaton
  • Integrate with Jira to facilitate bug reporting.
  • Intuitive use. There is a steep learning curve.
  • More streamlined method of adding licenses. Currently it takes a long time to get a new license when I add staff.
Video conferences and the ability to get live training sessions help.
Score 10 out of 10
Vetted Review
Verified User
We use qTest for our test cases and requirements repository, as well as tracking test cases execution status. The business problems qTest addresses for us is having traceability of feature requirements to test cases creation, manual test execution and automation status. Also ability to assign test cases to individual testers, create test plans for different releases, and run reports on them. Having the ability to integrate with Jira was crucial to support our SDLC. Most of the application teams within SAP Ariba is using qTest for the above purposes.
  • Ease of integration with Jira
  • Ability to customize test case properties
  • Easy to organize and create test plans and having visibility to statistics and execution summary.
  • Data query is slow for large projects (64109 test cases). It's not usable because the screen won't even load.
  • It would be nice to be able to add user to groups directly within the individual user Action menu. Instead of having to create user, assign projects, then go to Groups to add the user.
  • Some simple filtering with the search function or make it context based. So that if I am in Test Design tab, and I run a search, provide results for TC's only. Right now it returns everything from Requirements and Test Runs, etc.
qTest is well suited for software development teams both running Agile, Waterfall, or hybrid models. It's well suited also for any teams who use Jira for stories and defect tracking and want to have seamless integration.
Score 5 out of 10
Vetted Review
Verified User
We use Tricentis qTest Explorer to capture objective evidence of the testing we perform for our software products. The fact that it automatically captures screenshots as we perform our testing, including things like text typed in fields, is valuable because it allows our testers to focus on actually testing the product instead of the procedural work of recording every step they took in the process.
  • Capturing screenshots automatically
  • Capturing user inputs automatically
  • Exporting Tricentis qTest Explorer session reports is clunky, and it's easy to forget that you have to enable popups for the domain or nothing will seem to happen
  • It would be nice if the domain we chose when signing up was actually included in the URL
  • Some of the management features are a bit confusing to navigate, like adding a user to the right projects after giving them a license
  • When running in MS Edge, we noticed that the Tricentis qTest Explorer report indicates the browser as Chrome.
  • It's difficult or not possible to use inside VMs or on Linux. We've also had scenarios where using the web extension for Tricentis qTest Explorer slowed our product under test down too much to be able to use it.
I've only used the Tricentis qTest Explorer portion of Tricentis qTest (I recall some of the test management stuff being too clunky and prescribed to fit our workflow, so we chose a different tool). It's well suited for automatically capturing screenshots of browser-based or Windows-based applications during test sessions. However, we've had difficulty getting it to work well in other contexts, such as inside a Virtual Machine or on Linux.
Score 4 out of 10
Vetted Review
Verified User
Our organization used Tricentis qTest to document automated and manual test cases. Tricentis qTest was the first dedicated tool we've ever used to document test cases, and it was sorely needed because there was no single repository/source for our applications' use cases. Having a dedicated tool for this allowed us to organize and crowd-source our tests, and it made the reuse of tests significantly easier and cleaner.
  • Highly customizable: we were able to organize our test cases in unique ways that made our work easier.
  • Connectivity with Jira: being able to pull requirements information in from Jira was a big point for us.
  • Standalone tool: Being a standalone tool on a dedicated server, we were able to have access to our tests regardless of whether our Jira server was down.
  • Tricentis qTest wasn't particularly easy to use, especially for an organization that had not previously used to test case management tools. While there were a lot of things that you could do, the complexity made it difficult to just get started.
  • Not necessarily a comment about the tool itself, but the support that we got (or rather didn't get) from Tricentis left a lot to be desired. We were left to figure out a lot of things on our own. Training and product documentation was also lackluster.
  • The dedicated licenses were very expensive for a fledgling QA team. This prevented us from having enough licenses for everyone on the agile team to work with test cases. This was particularly painful because the full "read-write" license was required for anyone to just view test cases, a point that Tricentis sales staff misled us on.
  • The connectivity with Jira was temperamental and took an insane amount of time to set up the end to get working reliably. Support didn't work U.S. hours, requiring us to sync with them during early morning hours.
I believe that Tricentis qTest is optimal for organizations that have well-established quality practices, large budgets, and a solid idea of how they want to maintain their test cases. It might also be more suited to organizations that have a more waterfall work style because of the costs associated with multiple licenses required for product, development, business, and QA elements to individually collaborate. In our experience, this tool is not appropriate for smaller quality practices, that are trying to get a feel for how they want to organize and maintain their test cases.
Nick Larsen | TrustRadius Reviewer
Score 1 out of 10
Vetted Review
Verified User
qTest is our test case repository. We have a 2-way integration with Jira, which we use as our defect and requirements management software. We also use the Sessions module of qTest as our evidence collection tool. Finally, we report on test execution and test coverage from qTest to submit as a deliverable to our internal audit team.
  • The organization aspects of qTest are very good.
  • When Sessions does not interrupt testing by bogging down system resources, it is helpful.
  • Parameters is a great module that we have not taken full advantage of.
  • Customer support has been abysmal since Tricentis took over qTest.
  • Over time, it feels like the app is getting worse and worse from a performance, reporting, and integration perspective.
  • Returning to support, a user should not have to write an email to support learning how to file a ticket on the support portal. The support portal could be MUCH more user-friendly.
  • Locating CURRENT documentation for qTest is difficult. Once it is found, the documentation is confusing and often redirects to broken links. Recently, for example, there was verbiage that seemed to indicate that qTest was end-of-life. When I attempted to get clarification on this, Support sent me a link to the document that cause the confusion in the first place.
  • When we signed on to qTest, we had a dedicated relationship manager. That lasted until shortly after the Tricentis takeover. This was very important to me as I am a high-touch client.
I would recommend spreadsheets for test case management before I would recommend qTest. The primary reason for this is the Tricentis support model. Second, when comparing the costs of qTest versus almost any other competing tool at a similar tier of functionality, qTest is vastly more expensive. For that added expense, I would expect exceptional support and/or functionality, and that is just something you don't get here.
The actual answer is 0. I have never experienced worse support, whether personal or professional.
qTest is actually intuitive and user-friendly, despite my other scathing review aspects.
Score 2 out of 10
Vetted Review
Verified User
The primary use case for us involves the management and execution of acceptance and regression test cases as part of our quality assurance process. qTest is tightly integrated into our Jira instance which allows us to pull requirements into qTest and build test cases against them. qTest is also used for our bi-weekly regression testing which consists of manual and automation efforts. The automation test framework utilizes the qTest API to return the pass/fail statistics from each test run for an aggregate view of overall regression testing status.
  • Test Case organization and presentation
  • API functionality
  • Simplistic UI
  • Jira Integration
  • Sluggish UI and frequently degraded performance
  • Lacking simple keyboard interactions like shift-clicking to select a list of test cases
  • Dated UI with minimal user benefitting improvements over the years
  • No support for Jira advanced roadmap fields such as 'Teams'
  • Slow and unhelpful customer support
For the primary use case, I described in the first answer qTest satisfies those needs when it comes to building and organizing test cases. qTest is also suited to be fine for executing and providing status updates on test cases. qTest is not known for innovation, primarily after the Tricentis acquisition. UI could use additional user experience feedback. qTest does not appear suitable for properly handling the storage of years worth of test cases/suites/runs. Performance is inadequate. There does not appear to be any improvements insight for the performance or usability of the application.
February 12, 2022

qTest to the rescue!

Score 8 out of 10
Vetted Review
Verified User
Over Test case management including design, execution, and reporting.
  • Good user experience
  • Test Case Management functionality
  • Integration with our Test Automation suites
  • Integration with Azure DevOps
Integration with our Azure DevOps Scrum boards can be improved.
Score 1 out of 10
Vetted Review
Verified User
Tricentis qTest is used to manage and run our test cases for our confined animal software project. We have a pretty typical wet-agile development lifecycle, and I would have to imagine we are a typical use case.
  • The ability to export test cases to other mediums
  • Navigation and search capabilities of the test case repository
  • Jira integration is very problematic and after three years it still does not work as it should ( after many support calls )
  • Jira plugin version is not kept up to date consistently and has delayed our projects before
  • Setting up test case UI is confusing and cumbersome, eventually got used to it
  • Customer support is hit and miss, some agents are helpful and friendly but we have had a few that are simply rude
  • We were actually told by the sales team that our team of seven was so small that they no longer wanted to do business with us. I can understand if the company only wants to target larger, enterprise customers, but in my opinion, that needs to be stated clearly on the website
  • We have had several instances of downtime in the cloud, not sure what the SLA is
The product itself is mostly well suited for our company. We are not a large, enterprise establishment, and it works fine for our typical software development scenarios. We don't really have any exceptional cases where it does not.
Carla Borges | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
QASymphony is used by the entire organization and the developers. We use it to make a set of step-by-step test designs, a test to cover each characteristic of the product, or an aspect of a characteristic. This tool allows us to add additional tests to the reference test set at any time, so that we can add a test that covers a particular software defect or a new test of a newly added function.
  • It allows designating a single group of tests as part of a particular milestone, a set of regression tests to ensure that a product change does not leak into related areas.
  • Has the ability to integrate with Jira for tracking purposes to create stories and subtasks and link them directly to test cases.
  • It helps navigate between test cases and keep them all in a single repository.
  • It is difficult to configure all the technologies.
  • It should be possible to use any version of Java.
  • You have to configure Redis, Elasticsearch and, Java before you can install.
  • Sometimes [there are] loading issues.
It is very appropriate to connect all test cases with the user's history and connect with all JIRAs with TCs. By saving all the test documents in one place it gives us a lot of order and ease of use allows to run my test cases in different browsers and have the execution of the test for each execution separately and very useful your automation script for our requirement, but I'm still exploring in that area. should have some built-in tool to capture the screenshots.
May 22, 2018

Insights for test

Anvesh Malhotra | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
It is used across the organization. All tests either manual or automated reside in QASymphony. It solves release status, code coverage, efforts, and defects.
  • Easy to use GUI
  • Insights
  • Jira integration
  • CI implementation with Insights. Need to have information regarding CI builds
  • SauceLabs and Applitools integrations
  • Notifications are managed at project level instead at user level. This is pretty annoying. I configured CI integration using my user and now I receive hundreds of email.
  • Easy to structure a test.
  • Field settings are really user-friendly.
  • Test design templates for test designs are structured. Although it's not a tool for viewing your CI dashboards.
Return to navigation