Re: Comparing the various ways to run tests

Brad,

There are several advantages (but no hard & fast rules) for separating your
unit test code from your application code (if that is indeed what you are
asking):

   - Keeping your test code in a separate assembly(ies) allows you to
   ship your app without bloating it with unit tests (for me there's usally
   about a 2-to-1 ratio of test code vs app code)
   - It's easier to track realistic code coverage if you don't have to
   filter out the test code from the assembly under test.
   - It just plain FEELS cleaner (OK, that's not nearly objective, but
   hey.)

There are folks in both camps, some keep test code in the same assembly, but
I believe most try to keep them separate.
Thanks,
Doug
http://agileer.com



> From: "Brad Stiles" <[email protected]>
> Subject: [Nunit-users] Comparing the various ways to run tests
> To: <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
>        reply-type=original
>
> What are the advantages and disadvantages of running NUnit on the tested
> assembly directly, rather than on an NUnit project or a Visual Studio
> project or solution?
>
> I've always just created one assembly for my relatively simple projects,
> even if they are large, and organized via namespace in the test
> assembly.  Is it just that for projects that have more than one test
> assembly, an NUnit project or VS solution makes organization easier, or
> are there other benefits?
>
> Brad
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Nunit-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nunit-users