Home/ Questions/Q 377483
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T14:42:04+00:00

I thought it will be a common question so I searched for a while

  • 0

I thought it will be a common question so I searched for a while but couldn’t find it.

I am about to start a new project (C#, .net 3.5) and I was thinking about where I should I write the unit test code. I can create a unit test project and write all code there, or I can write the unit test code with the “class under test” itself.

What do you recommend and why? Things to consider before choosing an approach (caveats?)?

EDIT: About writing unit-test code with “code under test”: Removing the test code from production assembly isn’t difficult I guess. Thats what conditional compilation is for. Right?

Just throwing this point because answers are rejecting the second option just because production assemblies would be fatty.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Separate project, same solution. Use InternalsVisibleTo if you want to access internals from the test code.

    Separating out test from production code:

    • makes it more obvious what’s what
    • means you don’t need dependencies on test frameworks in your production project
    • keeps your deployed code leaner
    • avoids including test data files in your deployment assembly

    Keeping the code in the same solution:

    • keeps the test cycle quick
    • makes it easy to hop between production and test code
    • 0