We performed a comparison between SpecFlow 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."The initial setup is easy."
"One of the most valuable features of SpecFlow for us is its risk identification capabilities."
"The most valuable feature of the solution is unit testing...It is also an easy-to-use and user-friendly product that can easily adapt to any framework."
"SpecFlow's best feature is the ability to add additional layers to the programming."
"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."
"The solution's real-time integration with JIRA is seamless."
"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."
"Works well for test management and is a good testing repository."
"UI and UX are pretty easy to understand without much of a problem."
"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."
"Regarding improvement, it would be good if SpecFlow could provide chain testing, which it currently doesn't allow."
"I'd prefer in TFS if we could be writing test cases, not in the old classical version. We should be writing in Gherkin and then automatically have it convert that Gherkin test case into SpecFlow feature files."
"SpecFlow would be improved with the addition of functionality reporting, which would be really helpful for automation testing."
"SpecFlow's installation and configuration can be a bit challenging due to its flexibility as an open-source tool."
"Could use additional integration so that there is a testing automation continuum."
"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."
"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."
"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."
"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."
"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."
"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."
"The support for Tricentis qTest has room for improvement. The response could be better."
SpecFlow is ranked 9th in Test Management Tools with 4 reviews while Tricentis qTest is ranked 6th in Test Management Tools with 16 reviews. SpecFlow is rated 7.2, while Tricentis qTest is rated 8.4. The top reviewer of SpecFlow writes "Ensures efficient testing and validation of both business and technical requirements". 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". SpecFlow is most compared with Tricentis Tosca and TestRail, whereas Tricentis qTest is most compared with Tricentis Tosca, OpenText ALM / Quality Center, TestRail, Zephyr Enterprise and Helix ALM. See our SpecFlow 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.