This sounds very intriguing, and not just because of the immediate problem I'm trying to solve- but I won't go into that for the moment.

I guess the big question is, how does QA validate the binding code? The notion that they may not be testing what they think they are testing due to a bug in the binding code is pretty scary.

Other less important questions- when are these BDD scripts created? I could see QA doing this while devs are working on the feature, meaning that there is a lot less strain on QA near the end of the sprint. Are you using TDD and this testing is supplemental? I've never really understood if BDD is supposed to replace or supplement TDD. It sound supplemental to me (TDD is design and unit testing, while BDD tests broader scenarios). How much developer time is required for the bindings? I assume this would lessen over time as you'll have coded some reusable pieces (use is logged in as admin, etc).

Sorry for all the questions- but this idea has real promise and I'd like to know as much as I can before bringing it up to our project manager (I will probably download specflow this weekend and attempt to generate some scenerios avainst an existing resource).