This question has been bothering me lately, more from the fact that in the past this is something I would never do, yet in the past I wasn't writing BDD tests. Since incorporating SpecFlow into a Test Framework to use for verifying functionality in my Test environment I saw some use for those test scenarios to be used in verifying Production deploys. The current Framework verifies some of the Business Use Cases and is run whenever we push a new code package to the Test Servers. Some of those Use Cases I have been running against Production whenever we do a code push to there, but in some ways this seems wrong to me. I don't want to have to rewrite tests in a different framework, but I also feel like it would be better to have confidence in our deploys and its simpler to be able to do my checking with one framework. Currently the tests are divided into two separate frameworks but for ease of use I want to combine them, but am not sure its a good idea or the proper thing to do.
There is really only me who can Test/Check code, sometimes it's hard to bounce these ideas and thoughts on improving the tests off other people so usually I muse about it for awhile and then go ahead. I built up the Framework to relieve myself of having to do some basic, repetitive Use Cases so I can concentrate on other, more detailed Use Cases. We do get value from the SpecFlow tests, and have found serious issues in both Test and Production so there is buy in from my Managers as to the value of having this framework in place.
If you are running SpecFlow how do you handle your tests for Test and or Production? Are they the same? Is there something different I could be doing to add to the value the Frameworks are providing?