When we are designing a new system, one of the tools we use is user stories. User stories allow us to define what the feature should do from the view point of the end user. This way we take a user centered approach to designing the system. These are also used as part of our functional testing when writing code (plugin, JavaScript, etc.) to make sure what was written matches the user story. Even if we use Test Driven Development (TDD) we could easily miss some of the key functions within the feature and need to go back to our code to make changes and then restart our testing process. This can be time consuming. Wouldn't it be better to start our testing off with the user story? With advancements in frameworks and technology we now have the capability to write test scripts directly from the user story using SpecFlow . Taking this approach is known as Behavior Driven Development (BDD) because we are testing the users interactions instead of just ...
This is my blog about my experiences working as a software developer, consultant and systems integrator. I primarily focus on Microsoft Dynamics 365, Microsoft Azure, and Scribe Online.