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

Inflectra SpiraTest vs Tricentis qTest comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 16, 2024

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

Inflectra SpiraTest
Ranking in Test Management Tools
17th
Average Rating
7.4
Number of Reviews
25
Ranking in other categories
Application Requirements Management (11th)
Tricentis qTest
Ranking in Test Management Tools
4th
Average Rating
8.4
Reviews Sentiment
7.5
Number of Reviews
16
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the Test Management Tools category, the mindshare of Inflectra SpiraTest is 1.0%, up from 0.9% compared to the previous year. The mindshare of Tricentis qTest is 16.4%, up from 9.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools
 

Featured Reviews

Jason Lopez - PeerSpot reviewer
Intuitive enough and easy to learn, but in terms of folder organization, it could be better
Inflectra SpiraTest is the new kid on the block compared to Jira and Azure. Still, when I started exploring the tool, I realized that it was no different from other tools I've used in the past, but it all boils down to adaptability because the features would always be more or less the same. I found Inflectra SpiraTest intuitive enough. It's also easy to learn, so this is what I like about it.
Sudipto Dey - PeerSpot reviewer
It doesn't require installation because you can use it through the URL; it's user-friendly and has an excellent reporting feature
The support for Tricentis qTest has room for improvement. The response could be better. There's a feature I want to document on the Tricentis Idea Portal for Tricentis qTest, which I hope to see in the next version of the tool. It's a feature available in Micro Focus where you execute a test, and then on a spec level, you mark it as pass or fail. Then at the overall level, Micro Focus will automatically mark the test as a pass if all steps passed or failed, even if one step failed. However, here in Tricentis qTest, you still need to mark the overall level of the test cases. It's not automated, unlike what you have in Micro Focus. If Tricentis adds that feature in Tricentis qTest, it will make life easier for testers.

Quotes from Members

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

Pros

"The reporting functionality helps vendors and technical resources identify bugs and issues that need to be addressed. The simple dashboard-style home page makes training end-user testers simple and straightforward. The actual testing UI is VERY straightforward and very intuitive for the end-users that test the system since very often we pull from business and operational users to help test new systems."
"We were able to add a step-by-step procedure for someone to follow to assist in testing."
"The ability to reuse test cases already used across projects is the most valuable feature of this solution. We don't need to create new ones."
"Inflectra SpiraTest has a lot of functionality, which is good."
"The user-friendly features are the most valuable. For example, migration of requirements and migration of test cases and the creation of traceability. You have various reports that you need. The plug-ins that are available to connect with the other tools."
"I found Inflectra SpiraTest intuitive enough. It's also easy to learn, so this is what I like about it."
"The features of this product most valuable to me were the test case management and the visual status, by which it was displayed."
"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."
"Works well for test management and is a good testing repository."
"The most valuable feature is reusing test cases. We can put in a set of test cases for an application and, every time we deploy it, we are able to rerun those tests very easily. It saves us time and improves quality as well."
"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."
"I like the way it structures a project... We're able to put the test cases into qTest or modify something that's already there, so it's a reusable-type of environment. It is very important that we can do that and change our test data as needed..."
"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."
"The integration with Selenium and other tools is one of the valuable features. Importing of test cases is also good."
"UI and UX are pretty easy to understand without much of a problem."
 

Cons

"The UI for managing test cases, test sets, test runs could be a little more integrated, currently, these feel disjointed at times and confusing. Also, the test steps page needs to display the test steps closer to the top of the UI so as to not have to scroll down to find."
"Migrating is not very easy. It depends on the organization, how efficient and effective the decision-making process is. The plug-ins should be easier and more integrated rather than the user trying to integrate the tools which are more popular, like Jira et al."
"The user interface is slightly complicated and not very consistent. It could be more user friendly."
"Two areas that can stand improvement: integration with third party products and making it more intuitive."
"Being able to add scripting for testing can and does save a lot of time. When you are able to just ‘run’ a test case rather than manually add it and run it."
"It should develop integration with JIRA. We have some complexities which caused us not to decide to integrate it with our JIRA, like synchronous data."
"The folder organization in Inflectra SpiraTest could be better, though I cannot comment whether that is structure-related. Most of what I need would probably be in the tool, but as a test manager, I need to be able to create dashboards and reports easily."
"You can add what I believe are called suites and modules. I opened a ticket on this as to what's the difference. And it seems there's very little difference. In some places, the documentation says there's no difference. You just use them to organize how you want. But they're not quite the same because there are some options you can do under one and not the other. That gets confusing. But since they are very close to the same, people use them differently and that creates a lack of consistency."
"I wouldn't say a lot of good things about Insights, but that's primarily because, with so many test cases, it is incredibly slow for us. We generally don't use it because of that."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"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."
"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."
"I really can't stand the Defects module. It's not easy to use. ALM's... Defects Module is really robust. You can actually walk through each defect by just clicking an arrow... But with the qTest Defects module you can't do that. You have to run a query. You're pretty much just querying a database. It's not really a module, or at least a robust module. Everything is very manual."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
 

Pricing and Cost Advice

"I Googled the pricing for Inflectra SpiraTest, and it's about $4,000 annually."
"The pricing was excellent. I would recommend the enterprise solution."
"Our license price point is somewhere between $1,000 and $2,000 a year."
"We're paying a little over $1,000 for a concurrent license."
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
"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."
"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."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"It's quite a few times more costly than other tools on the market."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
830,726 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Financial Services Firm
14%
Manufacturing Company
12%
Healthcare Company
8%
Financial Services Firm
14%
Manufacturing Company
12%
Computer Software Company
12%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Inflectra SpiraTest?
I found Inflectra SpiraTest intuitive enough. It's also easy to learn, so this is what I like about it.
What needs improvement with Inflectra SpiraTest?
The folder organization in Inflectra SpiraTest could be better, though I cannot comment whether that is structure-related. Most of what I need would probably be in the tool, but as a test manager, ...
What is your primary use case for Inflectra SpiraTest?
The use case for Inflectra SpiraTest is to report on defects. It's also useful for writing test cases.
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?
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.
What needs improvement with Tricentis qTest?
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 expe...
 

Comparisons

 

Also Known As

SpiraTest, Spira
qTest
 

Overview

 

Sample Customers

- Morningstar - Deutsch Bank - Sopra Group - Booz Allen & Hamilton - UBS - US Government
McKesson, Accenture, Nationwide Insurance, Allianz, Telstra, Moët Hennessy-Louis Vuitton (LVMH PCIS), and Vodafone
Find out what your peers are saying about Inflectra SpiraTest vs. Tricentis qTest and other solutions. Updated: January 2025.
830,726 professionals have used our research since 2012.