I'm not quite sure if this is the place to direct this question but it sure brushes on the subject on BDD.
In my opinion the greatest use and benefit of using BDD is the communication within the team. For example using Cucumber-based frameworks you can write executable specifications in a langauge that the business people can not only read and understand, but maybe even write.
However where I have introduce these concepts I often run into questions surrounding traceability or connections to the current tracking system. My customer uses Team Foundation Server (TFS) and the first questions they asked was how to connect the executable specifications to work item within TFS. "How can we keep track of the work item flow through all it's phases; from vision, requirements, development, testing, bug reporting, maintenance etc".
So now finally to my question, does any body have / know of / has ideas on best practices for feature management in electronic tracking systems (such as TFS or JIRA).
Is the best thing to write the specification in .feature (FIT-table, Java-code or whatever) and link that to a work item?
Or would I be better of by generating the .feature-file from the text in the WI, since many tools works best when you to write the features in an IDE (such as SpecFlow and Visual Studio for example).
Or should I simply let the writing of the .features be a part of a developers work, to finish a story. I.e. you discuss the item and document it in the electronic tracking system and then create the .features separately from that? I don't like this since it violates the nice DRY-ness of having a single document (the .feature-file) for specification, test, regression test and development spec.
Please correct my mis-thinking in this and point me to a brilliant solution.
You received this message because you are subscribed to the Google Groups "Behaviour Driven Development" group.
To post to this group, send email to behaviordriv...@googlegroups.com.
To unsubscribe from this group, send email to behaviordrivendeve...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/behaviordrivendevelopment?hl=en.