Re: SuiteAttribute, RowTest and IterativeTest

Hi Kelly, 

> >  True enough. My real preference is not to have any user objects  
> > floating around at load time. :-)
> 
> Ok, then to do Theory 

Whatever that is. :-)

> we would have to have some kind of two 

three?

> stage approach. The first Load stage would load the tests,

We're thrashing here, so I need to ask some "obvious" questions.
First one: what do you mean by "load the tests?" 

> the second stage would "load up" the Theories,

And what does this mean?

> then the third 
> stage would execute the tests... now the second and third 
> stages could be interleaved, if that's helpful, but I don't 
> see a way to get around that, and support Theory as I understand it.
> 
> There has to be a stage, for example, where you could 
> generate random or semi-random values to pass into tests to 
> do Agitator type things.

OK - that's another term to define. In my understanding, 
"agitator type things" would mean modifying the code to see
if it breaks. But I'm pretty sure that isn't what you mean.

> This should not be in the Load stage, so it would have to be 
> done later, right?

I don't know. I'm really not understanding your proposal.

I have a suggestion. This talk is getting into specific
implementation details, which is appropriate for this list.
OTOH, you have said several times that you aren't familiar
with how NUnit currently loads tests. I think you need
to get familiar with the internals in order to fruitfully
discuss how we are going to change them.

Alternatively, we could dial the detail back a little
and talk about what you would like to be able to do
eithe as a test-writer or as an extension-writer.

I'm OK either way.

Charlie



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