-
Book Overview & Buying
-
Table Of Contents
Visual Studio 2010 Best Practices
By :
There's nothing stopping your test classes from being in any of your projects, even EXE projects (starting with Visual Studio 2005). So, you could have your tests in the same assembly as the classes that you are testing.
I haven't seen any particular arguments for or against separate test projects that are especially persuasive for every situation. For a "production" project (as opposed to "enterprise"), you can't redistribute a third-party testing framework. The easiest way to ensure this doesn't happen is to have a separate test project.
Context: Software under development is being delivered outside the organization.
Practice: Have separate test projects so that they do not need to be deployed into environments they are not needed.
Change the font size
Change margin width
Change background colour