We performed a comparison between Inflectra SpiraTest and Tricentis qTest based on real PeerSpot user reviews.
Find out in this report how the two Test Management Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Inflectra SpiraTest has a lot of functionality, which is good."
"I found Inflectra SpiraTest intuitive enough. It's also easy to learn, so this is what I like about it."
"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."
"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."
"The features of this product most valuable to me were the test case management and the visual status, by which it was displayed."
"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."
"We were able to add a step-by-step procedure for someone to follow to assist in testing."
"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."
"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 I found most valuable in Tricentis qTest is that it doesn't require installation. You use it through the URL. It also has an excellent reporting feature."
"The solution's real-time integration with JIRA is seamless."
"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..."
"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."
"UI and UX are pretty easy to understand without much of a problem."
"The JIRA integration is really important to us because it allows our business analysts to see test results inside the JIRA ticket and that we have met the definition of "done," and have made sure we tested to the requirements of the story."
"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 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."
"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."
"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."
"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 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."
"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."
"Could use additional integration so that there is a testing automation continuum."
"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 user interface has a somewhat outdated design, which is certainly an area that could be improved."
"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 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."
"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."
"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."
Inflectra SpiraTest is ranked 17th in Test Management Tools with 25 reviews while Tricentis qTest is ranked 6th in Test Management Tools with 16 reviews. Inflectra SpiraTest is rated 7.4, while Tricentis qTest is rated 8.4. The top reviewer of Inflectra SpiraTest writes "Intuitive enough and easy to learn, but in terms of folder organization, it could be better". On the other hand, the top reviewer of Tricentis qTest writes "Puts all our test cases in one location where everyone can see them. qTest also allows the segregation of different types of Testing". Inflectra SpiraTest is most compared with Microsoft Azure DevOps, Jira, IBM Rational DOORS and Jama Connect, whereas Tricentis qTest is most compared with Tricentis Tosca, OpenText ALM / Quality Center, TestRail, Zephyr Enterprise and TFS. See our Inflectra SpiraTest vs. Tricentis qTest report.
See our list of best Test Management Tools vendors.
We monitor all Test Management Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
