We are a Microsoft shop, have a reasonably mature technology stack and have very skilled .net resources. We have been using TDD since we started and now are venturing into the BDD space. Our work is delivered by agile teams, using strong agile practices.
Our end testable product is web, wpf and windows forms.
The testing resources have introduced BDD and would like to learn and use Ruby and Cucumber to perform the testing. There has been some resistance from the developers, as we would prefer to stick with the same technology stack and use Specflow (or similar). The argument from the testers is that it is simpler to learn.
I want to be sure that the developers and testers are not being biased, and that it is worthwhile introducing another technology.
We have a similar setup, we have testers writing and implementing steps behind scenarios. Our testers are quite happy staying with .net and c#. I think that if you introduce another technology you would have developers not running the tests before they commit and not taking responsibility for the tests when they fail as it would be extremely hard to debug it. This would mean your build would be broke more than it’s working.
It would probably be good to start for the testers to write the scenarios and passing them to development to be implemented by the developer that is going to introduce the feature into the application. They can then perhaps pair up with the developer and implement the scenarios together until they are comfortable doing it themselves.