Yes, there is, but the big problem is that it's good to do TDD and understand how Sepcfication By Example (like SpecFlow) fits in, I would recommend you a little deeper.
If you start with Gojko Adzic http://gojko.net/2011/02/04/tdd-breaking-the-mould/ , then he hopefully sets up a big picture. I would recommend paying close attention to a section with a seven-step tdd section or a double talk cycle. For me, the example specification is the outside circle when we receive a new business requirement, encode it in Gherkin and use Specflow to verify that the function does not work yet.
Then I recommend using TDD to technically help develop your code. Use several tests to shape development in order to achieve your business goal. With the Keith Braithwaite TDD Dome , as if you mean the exercise, I really recommend you go for it.
Finally, your TDD manages your specification, and at this point I would recommend that you consider reorganizing everything, consider your production code, your unit tests, and even your specifications to simplify and remove duplicates. Clean it.
Good luck.
Alski source share