qTest, a glorified spreadsheet for centralized test case management that offers some additional functionality for integration & automation.
Updated February 15, 2022

qTest, a glorified spreadsheet for centralized test case management that offers some additional functionality for integration & automation.

Anonymous | TrustRadius Reviewer
Score 2 out of 10
Vetted Review
Verified User

Overall Satisfaction with Tricentis qTest (formerly QASymphony)

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
  • Better organization and centralization of test cases has led to more cohesive team collaboration
  • Speed to delivery, deployments to production, are mostly maintained
  • Performance issues have led to testing delays requiring the team to switch to other methods which contributed to QA bottleneck issues and sometimes even missed sprint commitments
  • JIRA
qTest is primarily integrated with our JIRA cloud instance. While we have experienced integration issues sporadically in the past the token connection has been fairly reliable. Setup and maintenance is not difficult to achieve, however, when issues do arise a re-sync or reconnection might be necessary which can also sometimes create unnecessary duplicate data entries within qTest as a result.
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 feature coverage and risk assessment, we have had to rely on external data exporting in order to provide additional visibility since qTest does not provide a good solution for this. qTest data retention has allowed us to ensure quarterly and annual compliance is met.

Do you think Tricentis qTest delivers good value for the price?


Are you happy with Tricentis qTest's feature set?


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?

I wasn't involved with the implementation phase

Would you buy Tricentis qTest again?


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.

Tricentis qTest Feature Ratings

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