TDD

Test Driven Development

I intend on employing TDD techniques when developing and where possible keep it at the unit testing level i.e. avoid integration tests. However when dealing with the .NET Framework this is not always possible especially since Microsoft have a tendency to use sealed classes (that do not have interfaces) with private factories to instantiate some of these objects.

Because of TDD, the code tends to be what is required and no more i.e. do not expect to use any of the code in your own projects without some re-development, it is what I needed to meet each story and task; I am not building a generic framework.

Testing Tools

NUnit and Moq are my tools of choice on the .NET platform. I have decided to try Google Test for the C++ code. However this code deals very heavily with the RunTime and so these tests may be more integration tests than unit tests.

I am also using AppVeyor to gather the results of these tests.