Re: SuiteAttribute, RowTest and IterativeTest

On Tue, Mar 11, 2008 at 12:34 PM, Charlie Poole
<[email protected]> wrote:
>  > As for the pattern that we only call static methods at test
>  > load time, I think that might have to change as we go towards
>  > a full Theory implementation.
>
>  I guess that remains to be seen - bear in mind that I'm only
>  talking about user fixtures here. Although they shouldn't,
>  users often write test fixtures that create strange side
>  effects in their constructors - it's really weird when a
>  large machine in the corner starts up simply because you
>  looked at the structure of the tests. I saw that happen
>  in one shop, back when there was an error in NUnit causing
>  the instance to be created too early.

That doesn't sound good... Reminds me of the Microsoft advert...
"Cylons, why testing is important."

>  So, if we are going to create any user-instances at load
>  time, I would rather they be some other object than the
>  test fixture class.

Ok, but no matter what user instances you created at load time, the
could do stupid things, no? I don't think NUnit's users need to be
especially protected from themeselves. I suspect it is a rather well
educated group in general.

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