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.
I need to add unit tests for an existing solution with a lot of projects. Building the project takes a long time, so I decided to create another seperate solution for unit test projects. I don’t know what’s better: reference to dll or include in unit test solutions existing projects that I want to test.
How should I organize my test cases, and why? Please base answers on your own direct experiences.
I strongly suggest that you include the project you want to test in the solution and reference that project.
In one big project I referenced only the DLLs and had a lot of problems with the unit tests testing old versions of the DLLs, because building the unit test project didn’t automatically trigger a build of the project it tests.