SpecFlow Reviews

In our development workflow, we use SpecFlow as a BDD framework to bridge the communication gap between business and development teams. We create Given-When-Then scenarios in plain language using Gherkin syntax, allowing easy collaboration with stakeholders. Under the hood, we implement these scenarios in C#, aligning with our .NET environment. Our use cases range from backend testing, making API calls, to mobile testing with APKs using APM Inspect or APM desktop. SpecFlow's ability to integrate seamlessly with our CI/CD pipeline ensures efficient testing and validation of both business and technical requirements.

SpecFlow enhances our organization by translating logical understanding into executable code in our C# environment. Similar to Cucumber in Java, it converts scenarios into callable methods, promoting collaboration and code interpretation. The framework's features, such as tagging and data segregation, provide flexibility and reusability without altering the core code. This allows us to efficiently run tests in different environments with varying data sets, streamlining our testing process.

In my company, we use SpecFlow as an automation solution.

We are using SpecFlow to write down scenarios in Gherkin. And then, we put detailed coding in Selenium in C#. For the high-level sanity testing of the APIs, we use SoapUI for the SOAP APIs and Postman for the REST APIs.

With Cucumber and SpecFlow, the purpose of both is the same. We use a lot of Microsoft technology, so that's why we use SpecFlow. It helps us to write down the scenarios in Gherkin and write down the implementation of each step and scenario.

I don't see any other options. So that's why the only option for us to write down the Gherkin for the Selenium cases is the SpecFlow solution. 

The initial setup is easy.

It is stable. 

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.