How SpecFlow helps you handle these situations:
As a developer, you struggle with situations like:
Natural Language for Naming Tests
Regardless of how much you try to rename it to make more sense, it will not get better. Eventually, you give up and end up with method names of your automated tests:
Let’s hope nobody deletes that comment...
You write a normal sentence to describe what your test is doing.
With the added flexibility of adding a description to each test and not being limited to just English
Easy use of Examples
Struggle with translating examples into automated tests (e.g. example table handling) and wonder if your code still reflects the example. Can your stakeholder read code?
Define your examples in a nice, easily readable way with tables, readable for all stakeholders.
Make the value of testing transparent
Within the Developer's IDE 856/895 passed tests are reported.
Stakeholders discover the value of testing with their browser, which displays an auto-generated up-to-date documentation of your automated tests.
Explaining how the application works
You block 4 hours of your time to dig through the code and find the answer out on your own. Then you have an one-hour meeting to explain it to your product owner
You point them to your understandable and readable test cases, where they are able to easily fnd answers to their questions.
Use established Test Automation Libraries
Browser Testing with Selenium
Write your Test scenarios without the need to mention any Selectors or Element Ids. You can hide this implementation details in your automation layer.
API Testing with RestSharp
With SpecFlow you don’t need to work with raw JSON or any other messaging format in your tests.
You can use SpecFlow together with RestSharp to have a nice and clean interface to test your APIs.
Popular .NET Testing Tools
SpecFlow builds upon proven .NET testing tools. You can still use your beloved tools.
SpecFlow works on every current .NET implementation
on any supported operating system
in your favorite IDE