Getting Started with SpecFlow

In this video, Bas explains Behavior Driven Development, SpecFlow and the SpecFlow ecosystem. This is part one of a five-part video series by Bas Dijkstra.
Continue with part two and learn how to set up SpecFlow, write and execute your first scenario: • Write and execute your...
SpecFlow is the #1 .NET open source framework for Behavior Driven Development, Acceptance Test Driven Development and Specification by Example.
Learn more about SpecFlow: specflow.org/

[@thespeakingshutter8302]

This is just amazing . There is a lot of confusion and lack of awareness in the industry about 'Spechflow != BDD'.
Very well explained and to the point.
Kudos.

[@SpecFlowBDD]

Thank you!

[@NarutoUzumaki-mx1mo]

Thank you so much. this will be very helpful

[@SpecFlowBDD]

Glad it was helpful!

[@darktrick2235]

I would've appreciated an introduction to the actual software and not the concepts around it.
Do you have a quick overview video that can make it clear to me if this software will fulfill my business needs - or at least tells me whether it's worth spending more time evaluating?

[@adolfomq00]

It is possible to add subtitles in Spanish to your videos? Some people in our team are interested in making them available to non English speakers

[@SpecFlowBDD]

Sure. We activated that subtitles can now be contributed by the community.

[@adolfomq00]

@@SpecFlowBDD Thank for your quick answer, but unfortunately Google decided to remove that feature just yesterday!! As they posted here: support.google.com/youtube/answer/6054623?hl=en . We could create a subtitle file in a supported format and send it to you. I would like to know if you agree with that.

[@SpecFlowBDD]

*facepalm* Thanks Google, ...
Sure we agree to that. It would be fantastic when you create the subtitle file and send it to us. Please send it to [e-mail]. We will then upload it to CZcams asap. Here are the supported formats from CZcams: support.google.com/youtube/answer/2734698?hl=en

[@MarkDuivesteijn]

I'm familiar with Ruby + Cucumber (Specflow == Cucumber), but in the recent years I've noticed that people just skip BDD and only use Cucumber/Specflow. This should not be your first idea when setting up a test framework. If you ask me, I would say... Try to avoid Cucumber/Specflow whenever possible. Starting is easy, but there are so many pitfalls that it usually leads to more rework, more maintenance, more complexity and still no BDD. You don't need Specflow to make easy to read test automation.

[@SpecFlowBDD]

Yes, starting is easy. Mastering is the hard part. Do you have any suggestions how we could help our users to get there? Which kind of content would you look for? Are there features missing that would make it easier to master BDD/SpecFlow/Cucumber/Test Automation?

[@SuperArdave]

Does using SpecFlow automatically mean that I'm doing BDD?

[@SpecFlowBDD]

No. BDD is more than automating scenarios. Please have a look at specflow.org/learn/bdd/ to see, what the idea behind BDD is and when you use SpecFlow for it.

[@lost-prototype]

This shows nothing about how it's done.