VSTS Unit Testing Private Methods
I have been thrashing the unit testing abilities of VSTS lately and something my TL raised has set me thinking. The unit test wizard allows you to create unit tests based on your code (given that TDD requires unit tests first is another point), it allows you to select public, private methods and properties. My TL asked why privates, and its a very valid point. Given that unit testing is about testing all of your code via the public methods and ensuring that your tests run through all your private methods via the depth of your tests is a main stay of unit testing. VSTS includes code coverage tools so you can even check that your achieving this with your tests so why test privates directly, anyone.....