![]() Prove the PO that the « Definition Of Done » based on the « Given-When-Then » of the BDD is compliant.The Dev is naturally going to ask questions to the PO (Product Owner) and one of the aim of BDD is to force them to talk ! and have a common language without having any misleading specification.Implementer the Unit tests (helped by the BDD auto-generated code),. ![]() Write it down into Microsoft TFS / VSO, via Excel.OBJECTIVE: From a “regular” specification (waterfall way) we are going to: Without debating weather or not one should use BDD or TDD, this post focuses on how to do it the BDD way, and show that SpecFlow could handle easily French. Now that we have VSO, Visual Studio Online and Microsoft Azure, we can be even more Agile ! BDD (Behavior Development Driven) and TDD are topics that are not new (my first post was in 2011).
0 Comments
Leave a Reply. |