I am fairly new to unit testing, and have been recently using the Visual Studio Test Manager to create my Unit Tests. The way that I have currently been doing things is as follows:
- Create some libraries.
- Add the libraries to one big solution, along with the application.
- Create a folder called Tests that I put my Tests project into.
- Write unit tests for my libraries and stuff them all into the same folder called "Tests".
I run all of my tests, and this method seems to work for me. The reason I do it this way is that I sometimes feel I cannot create any practical tests unless all of the classes necessary for the application are actually present/involved in my solution.
Should I be creating tests as I create the libraries?
I don't see the practicality, and it seems to just create more overhead getting the work done because I would have to create tests again for my application anyway.