Re: Data-driven Tests in NUnit 2.5

Hi Kelly, 

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

Requiring a Type automatically catches things like spelling
errors and allows the code to be refactored by tools like R#.

It should cut out most of the low-level errors, but will
lead to a runtime error if your type doesn't implement
a required interface - just for one example.

However, the proof will be in the code. We're just
talking here.

Charlie

> -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/
> _______________________________________________
> nunit-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/nunit-developer
> 



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