NUnit

[Mark]

I'm using NUnit with an ASP.NET .dll ... looking for recommendations:

1. Put the Test class in the same project (.dll) as the class that is being
tested?
2. Put the Test class in the same namespace as the class that is being
tested?
3. Put the Test class in the same fodler as the class that is being tested?

What works best over the long haul?

Thanks in advance.

Mark

[Peter Rilling]

Actually none are the preferred method (in my opinion). I would create a
separate project that holds all your unit tests. The namespace you choose
is actually up to you, but I usually like to isolate them from the classes
being tested.

"Mark" <Ma**@nowhere.com> wrote in message
news:#v**************@TK2MSFTNGP12.phx.gbl...

I'm using NUnit with an ASP.NET .dll ... looking for recommendations:

1. Put the Test class in the same project (.dll) as the class that is being tested?
2. Put the Test class in the same namespace as the class that is being
tested?
3. Put the Test class in the same fodler as the class that is being tested?
What works best over the long haul?

Thanks in advance.

Mark

[Gerry O'Brien]

That is the procedure we follow here as well. Seperate project.

--
Gerry O'Brien
Visual Basic.NET MVP
"Peter Rilling" <pe***@nospam.rilling.net> wrote in message
news:em*************@TK2MSFTNGP14.phx.gbl...

Actually none are the preferred method (in my opinion). I would create a
separate project that holds all your unit tests. The namespace you choose
is actually up to you, but I usually like to isolate them from the classes
being tested.

"Mark" <Ma**@nowhere.com> wrote in message
news:#v**************@TK2MSFTNGP12.phx.gbl...

I'm using NUnit with an ASP.NET .dll ... looking for recommendations:

1. Put the Test class in the same project (.dll) as the class that is

being

tested?
2. Put the Test class in the same namespace as the class that is being
tested?
3. Put the Test class in the same fodler as the class that is being

tested?

What works best over the long haul?

Thanks in advance.

Mark