Re: Data-driven Tests in NUnit 2.5

"Kelly Anderson" <[email protected]> Fri, 21 Mar 2008 18:05:19 -0600
Newsgroups gmane.comp.windows.dotnet.nunit.devel
Message-ID <[email protected]>
On Fri, Mar 21, 2008 at 11:17 AM, Charlie Poole
<[email protected]> wrote:
> Hi Kelly,
>
>
>  > I'm still trying to come up with something that will produce
>  > a compile time error/warning, but nothing comes to mind yet.
>
>  Yes, that's why my hypothetical attribute takes a type. NUnit
>  would have to check that the provided type actually implements
>  the necessary interface.
>
>  It's awkward, but not a show-stopper.

The key benefit in my mind of type safety is compile time vs. runtime
notification of the problem. If you have to live with runtime, why not
use the simpler "string" approach? Or, do you see some other advantage
aside from compile time notification of type safety?

-Kelly

-------------------------------------------------------------------------
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/