Why  this extension ?

I work on Agile Projects where Unit-Testing are in the middle of all our development tasks. We work with a lot of Domain Expert and we found, with acceptance Test and Gherkin language, a way to reduce the gap between our teams. Now we are able to run automaticaly specifications written by domain expert and reduce the process of manual test acceptance.

SpecFlow allows to do Behavior Driven Development with a lot of simplicity but, in my opinion, there is again a little gap between written specification and unit test in Visual Studio.

In some projects, Domain Experts write specfication (In Gherkin language) directly in Team Foundation Server (they create a user Story, and add Test Cases to it). After that, the developer copy and paste each statements and create SpecFlows files to be able to run automaticaly the test.

This is what I want to avoid. I developed this extension to avoid these steps where the developper needs to find the user story in TFS and then copy and paste each statement in two File (SpecFlow Feature And StepDefinition). During this process, a lot of errors could occur and …yes, it’s boring to copy / paste from TFS to Visual Studio !

 

Process