Used it a bit on a previous project some years ago. I thought it actually worked pretty well actually, with some important caveats about use:
Because the implementation for each line in the spec binds to a static method, state management between the lines in the tests is an issue. Ideally you don't have any, but we did, and didn't handle it well, and ended up with methods originally written to back one test having baked-in assumptions about what state was available and where it was (static fields) that failed when that same step was reused in another test. This mostly came about because we were doing integration tests, and different tests were actually using different test rigs. I think provided you have a single context object that represents an instance of either your entire application (system testing) or a test rig that's consistent for all tests in a library (integration tests) it probably all works out ok, but we definitely found all this out the hard way. From: Kirsten Greed Sent: Tuesday, April 29, 2014 3:45 PM To: ozDotNet Hi All Not sure if this is OT or not, but is anyone using Specflow? I am wondering if the practice works in reality... www.specflow.org Thanks Kirsten
