This post has been republished via RSS; it originally appeared at: TestingSpot Blog articles.
First published on MSDN on Aug 29, 2018
Authored by Darren Rich
Behavioral Driven Development is becoming more critical as the expectations for software quality and fit for purpose are increasingly regulated by State, Federal and International entities. I was introduced to SpecFlow while working with customers who need to meet SOX compliance, remain highly agile and prove that they have automated tests enforcing the compliance. This has led to a series of blog articles centered around BDD.
As an example of SpecFlow Unit Tests the following could be actual source code…
Feature : Force Product Owners and Development to collaborate through process
Scenario: Describe a specific requirement with a structured language
Given A product owner wants a specific feature
And there is an established scrum team who might deliver it
And gets feedback from the scrum team
Then the scrum team will review it
And rewrite it with the PO until approved
BDD is a huge topic and I have a very short attention span as I assume you do too so I wrote a very short introduction to BDD with SpecFlow at: http://darrenrich.blogspot.com/2018/02/bdd-specflow-vsts-cicd-oh-my.html
Next I wanted to ensure that you could get your hands on working code quickly, under 15 minutes actually, and begin to play with BDD driving Selenium browser automation at: http://darrenrich.blogspot.com/2018/03/bdd-specflow-vsts-cicd-fnc15.html
If it doesn't work with VisualStudio.com release definitions I don't see the value in testing frameworks. In this article I go deeper into the ways that BDD SpecFlow can be integrated into your CICD pipeline at: http://darrenrich.blogspot.com/2018/04/bdd-specflow-vsts-cicd-digging-deeper.html