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

CucumberStudio vs Tricentis qTest comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

CucumberStudio
Average Rating
8.0
Reviews Sentiment
7.1
Number of Reviews
12
Ranking in other categories
Rapid Application Development Software (26th), Dynamic Application Security Testing (DAST) (8th)
Tricentis qTest
Average Rating
8.4
Reviews Sentiment
7.5
Number of Reviews
18
Ranking in other categories
Test Management Tools (3rd)
 

Mindshare comparison

While both are Quality Assurance solutions, they serve different purposes. CucumberStudio is designed for Rapid Application Development Software and holds a mindshare of 0.2%, up 0.0% compared to last year.
Tricentis qTest, on the other hand, focuses on Test Management Tools, holds 15.1% mindshare, up 12.5% since last year.
Rapid Application Development Software
Test Management Tools
 

Featured Reviews

Walter Wirch - PeerSpot reviewer
Facilitates integration of test scenarios while needing modernization of components
CucumberStudio is primarily used for designing test scenarios and automating testing. We have implemented it in conjunction with our own routines for integration into our infrastructure CucumberStudio aligns with our strategy for data-driven testing. It supports our product owners in designing…
SamuLehikoinen - PeerSpot reviewer
Efficient and collaborative software testing providing comprehensive test management capabilities, seamless integration with various tools and impressive manual regression testing features
The user interface has a somewhat outdated design, which is certainly an area that could be improved. Some of the modules appear to be loosely connected, but despite these aspects, our overall experience with the tool was positive. When you begin integrating your testing tools with qTest, the available examples may not be very clear, and I believe this is an area that could be enhanced, particularly in terms of providing clearer integration guidance. While the tool's integration with various testing tools is impressive, there is room for improvement in showcasing more cases and benefits, especially through additional videos and documentation.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The solution is stable."
"The most valuable feature of CucumberStudio is its use of action words, which allows me to avoid writing test cases from scratch for the most common scenarios."
"CucumberStudio aligns with our strategy for data-driven testing."
"The best thing is that a person without knowledge about the program can easily understand what happened in our testing process."
"The data table that helps in converting a single script to multiple test cases is very helpful."
"CucumberStudio has a very user-friendly interface."
"CucumberStudio aligns with our strategy for data-driven testing."
"The URL is very useful, and it has a very good UI for deploying information of the scenarios created."
"The initial setup was very easy."
"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."
"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."
"UI and UX are pretty easy to understand without much of a problem."
"The most important feature which I like in qTest manager is the user-friendliness, especially the tabs. Since I'm the admin, I use the configuration field settings and allocate the use cases to the different QA people. It is not difficult, as a QA person, for me to understand what is happening behind the scenes."
"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."
"The integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"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."
 

Cons

"Another kind of deployment might be useful, perhaps an option to install the tool in a local deployment."
"A key area for improvement is to revamp outdated components such as HipTest publisher."
"I think it would be better if we could also do the reporting with CucumberStudio."
"CucumberStudio's API integration could be improved both in terms of reliability and design."
"A key area for improvement is to revamp outdated components such as HipTest publisher."
"The reporting needs to be improved."
"I would like to see better customer support."
"For UFT to Tosca migration, scripts need to be rewritten as there are no automatic converters available."
"As an admin, I'm unable to delete users. I'm only able to make a user inactive. This is a scenario about which I've already made a suggestion to qTest. When people leave the company, I should be able to delete them from qTest. I shouldn't have to have so many users."
"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."
"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."
"The support for Tricentis qTest has room for improvement. The response could be better."
"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."
"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."
"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."
 

Pricing and Cost Advice

Information not available
"We signed for a year and I believe we paid $24,000 for Flood, Manager, and the qTest Insights. We paid an extra for $4,000 for the migration support."
"Based on whatever I heard, I can say that Tricentis qTest is a little costlier than other test management tools, like Jira, Zephyr, or Xray."
"We're paying a little over $1,000 for a concurrent license."
"It's quite a few times more costly than other tools on the market."
"For me, pricing for Tricentis qTest is moderate, so that's a five out of ten. It's more affordable than my company's previous solution, which was Micro Focus ALM."
"Our license price point is somewhere between $1,000 and $2,000 a year."
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
report
Use our free recommendation engine to learn which Rapid Application Development Software solutions are best for your needs.
865,484 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
22%
Manufacturing Company
18%
Financial Services Firm
10%
Transportation Company
8%
Financial Services Firm
13%
Manufacturing Company
12%
Computer Software Company
11%
Insurance Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with Hiptest?
CucumberStudio's API integration could be improved both in terms of reliability and design. The API requires data to be sent in a specific format, which takes time to build. Additionally, the repor...
What is your primary use case for Hiptest?
I use CucumberStudio as a test case repository. All of our test cases are stored there. It is also part of our test planning process. For every sprint, we plan the test cases in CucumberStudio and ...
What advice do you have for others considering Hiptest?
For teams following a BDD style software development approach, CucumberStudio is a great collaborative tool that covers all the basic requirements of a test management tool. I would rate CucumberSt...
What do you like most about Tricentis qTest?
I found the reporting aspect to be the most valuable as it provided a comprehensive overview of the efforts needed and the workload for individual tests.
What is your experience regarding pricing and costs for Tricentis qTest?
The solution is expensive. For the features that are available, depending on the volumes of licenses we get, we are able to get better discounts as strategic partners of Tosca. We can pass some ben...
What needs improvement with Tricentis qTest?
Customers are moving towards Tricentis due to their association with SAP. There is interest in understanding if there are connectors for converting UFT scripts to Tosca, as many customers are looki...
 

Also Known As

Hiptest
qTest
 

Overview

 

Sample Customers

Cisco, Cardinal Health, Intuit, Smartbox, Accenture, Deliveroo
McKesson, Accenture, Nationwide Insurance, Allianz, Telstra, Moët Hennessy-Louis Vuitton (LVMH PCIS), and Vodafone
Find out what your peers are saying about Microsoft, ServiceNow, Oracle and others in Rapid Application Development Software. Updated: August 2025.
865,484 professionals have used our research since 2012.