I see that this question already has an answer, and I have not tried NBehave. But we use MSpec (Machine.Specifications) for this rather large Enterprise project, and it works pretty well for us. Very well worth mentioning.
Rob Conieri produced an EXCELLENT BDD learning video where he uses MSpec line by line: (link removed, no longer available, but find it)
Learn more about Rob Conery's MSpec and why it uses it.
http://wekeroad.com/2009/09/21/make-bdd-your-bff-2/ You can also check his other posts with BDD tags.
Pros:
- Allows you to quickly "crop" your entire story, scene, contexts and specifications without actual code. Let you focus on the general โBehaviorsโ that are the goal of BDD !, without worrying about code and compiling it.
- Creates a REPORTING HTML report with the inscription "<- NOT IMPLEMENTED" next to the encoded specifications. I often pass this report: to the Client (CEO and CTO), The Testers, New Resources, which I bring to the project, and to anyone who wants to know how the software works, without having to show a line of code!
- TestDriven.NET runners are included in MSpec using the new tdnet binding (no configuration!).
- The [Behaviors] attribute, along with its Behaves_like type of delegation, copies existing specifications from one scenerio on top of another by using the snap function.
Minuses:
- There is little to the documentation, although not so much (see the video above). Recently, the author wrote about help with paperwork.
- Another new, and only a side project from the author (not his main concert). But he is very active in this post.
Hope this helps.
eduncan911
source share