Re: nunit-developer Digest, Vol 21, Issue 16

On Feb 13, 2008 10:34 AM, Charlie Poole <[email protected]> wrote:
> From my perspective, the point is that changing the timing of
> when objects are created is a /major/ change to NUnit. NUnit
> creates TestFixture and TestCase objects at load time, but does
> not populate them with user fixture instances until run time.
> The same TestFixture/TestCase object is used throug multiple
> runs in the gui unless you do a reload. A different user
> instance is created for each run.
>
> NUnit could work with a data provider much more easily if
> it were either (1) a static method, (2) a method on an
> entirely separate object or (3) a functor object.

I see no reason that couldn't be changed. I put the function in the
same class because that seemed easiest. If it's not, then there is no
real need for that. One of the things I'm interested in is keeping
things simple. If it were another object that just implemented an
IEnumerable interface, that probably would be pretty simple to grok.
I'm more concerned about ease of use than anything else on this deal.

> I'm very much into a full theory implementation in 3.0 but I
> see some issues with getting it into 2.5, which is after all
> only supposed to be a "quickie."

Fair enough... I was just wondering if it would be easy.

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