Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
For a long time we kept unit testing as a separate project/workspace that occasionally we attached to product project to run unit tests on the fly.
Recently we decided that the ability to run unit tests on the fly is really important for our daily work. To implement it in Visual Studio 2010 we put product and unit testing in the same TFS2010 workspace.
The huge drawback is that product and unit testing check-ins are mixed.
Is there any trick or better approach to avoid this problem?
Thanks.
Well, in my project we have used same workspace under TFS for both app code and unit testing but we had separate project for unittesting and haven’t mixed them with main project solution.
Again, in TFS they are stored under separate folder in separate branch.