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.
Currently, I am splitting all my tests by package (projects). So if I have 12 projects, I will create 1 more project for Unit Test with 12 classes that will test all my package.
Do you do the same way or do you have 1 testing class by class? How do you organize all your test?
Like Pokus my tests are in the same assembly as the classes to test so I can test internals and privates.
In C# you have Debug and Release builds, I add another called UnitTest with a compiler directive UNITTEST. I can then add the directive(#if UNITTEST) at the top of the test class, so that when I compile Debug or Release the tests are not compiled in, but when I compile UnitTest they are.
I add a folder called Tests that contain my test classes. Class1.cs has a test class Tests\Class1UnitTest.cs.
Maybe better ways, but this works for me.