Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Our company is looking at implementing BDD in our .NET application. Specifically, SpecFlow.

We can foresee a large number of common steps being created ('Given a customer', etc), so what methods have been used to document these, so that the business can reference them? Is XmlDoc on the step definition classes sufficient, or have others found better methods of documentation?

share|improve this question

closed as not a real question by gnat, thorsten müller, Walter, Yusubov, Robert Harvey Nov 29 '12 at 16:14

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 1 down vote accepted

The step definition report of SpecFlow provides the information, which steps have been defined, and whether and how often they are actually used, as well as which steps have no step definition yet. You can read more about it on the Reporting page of the SpecFlow wiki.

share|improve this answer
Thanks, Martin. I must have missed that - I knew about the execution report. – Daniel Becroft Nov 29 '12 at 20:43

Not the answer you're looking for? Browse other questions tagged or ask your own question.