SpecFlow Reviews

Name: SpecFlow
Brand: Tricentis
Rating: 4 (4 reviews)

3.6 out of 5

4 reviews
75% willing to recommend

What is SpecFlow?UNIXBusinessApplication
Price:

SpecFlow is a testing framework that supports Behaviour Driven Development (BDD). It lets us define application behavior in plain meaningful English text using a simple grammar defined by a language called Gherkin.

Get the SpecFlow Buyer's Guide and find out what your peers are saying about SpecFlow, Tricentis Tosca, TestRail and more!

SpecFlow is the #9 ranked solution in top Quality Management Tools. PeerSpot users give SpecFlow an average rating of 7.2 out of 10. SpecFlow is most commonly compared to Tricentis Tosca: SpecFlow vs Tricentis Tosca. SpecFlow is popular among the large enterprise segment, accounting for 66% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 15% of all views.

Helped 770,765 peers since 2012

Featured reviews

KreshenAmourdon

Software Automation Test Engineer at I2era

Jul 26, 2023

In our company, we need to maintain the scripts of the product daily, and in case of failures, we need to check out the scripts. I would recommend the product to those planning to use it based on both they are planning to build. If you are going for unit testing or small scripts, then you can go with SpecFlow. I don't have much experience with the solution. It is a good and straightforward product. It is also an easy-to-use and user-friendly product that can easily adapt to any framework. I rate the overall solution a seven out of ten.

Read full review

Shahid Manzoor

Software Quality Assurance Supervisor at a transportation company with 1,001-5,000 employees

Nov 10, 2022

There should be more integration with the application life cycle management tools, including integration with Jira and Azure DevOps. We used to write our test cases in Microsoft Azure DevOps, which were deployed on-premises. We would write test cases in a classical way and the test data within the test steps of the test case. When we have to write down the problem, we write scenarios in Gherkin and then automate them in Selenium. That said, there is no way to have traceability between the test feature files of this backflow with any work item in TFS, Azure DevOps, or in Jira. We cannot link them. While we can link the code, this feature file or this Selenium file cannot be properly linked. 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. There is room for improvement in managing the test data related to the test cases.

Read full review

Vijay Gaikwad

Technical Lead at a tech services company with 10,001+ employees

Sep 6, 2022

I use SpecFlow in my framework to add a layer with the English statements to my programming SpecFlow's best feature is the ability to add additional layers to the programming. SpecFlow would be improved with the addition of functionality reporting, which would be really helpful for automation…

Read full review

SpecFlow market share

As of April 2024, the market share of SpecFlow in the Test Management Tools category stands at 3.4%, marking an increase of 159.4% compared to the previous year, according to calculations based on PeerSpot user engagement data.

Test Management Tools

Key learnings from peers

Valuable Features

"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."
"The initial setup is easy."

Room for Improvement

"SpecFlow's installation and configuration can be a bit challenging due to its flexibility as an open-source tool."
"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."