spam: suspected: Re: [Mono-devel-list] patch for nunit support for xmlconf

Atsushi Eno atsushi at
Sun Jun 26 15:22:32 EDT 2005

Andrew Skiba wrote:
> Atsushi Eno wrote:
>> If you didn't need any comments, then you could just commit things.
>> But since you didn't do that, then what you asked is all readers'
>> comments. I'm just a reader here, without mentioning any kind of
>> "permission" and I think your way of answering is weird. No?
> Of course, I wanted comments, that's why I sent the patch to the list. I 
> just was afraid it will not have too much response. The next time I will 
> post it during the Boston working week.

I understand that it is likely to happen we don't receive any
comments, but in such cases the way to go is not to urge people
but to wait more :-)

> No, it's not integrated. Now I understand, what confused in my message.
>>     - if it is to generate a TestFixture class which contains
>>       Test case methods.
> Impossible to make. w3c opens different files but the code that opens is 
> the same. If I'd write regular TestFixture class, it would look like:


> And so on, 3000 testcases.

Yeah, that's what I had in mind you might created, by writing
kind of code generator. It's not that difficult, like iterate
test master file, call Console.WriteLine ("[Test]public void
TestBlah(){..."); and so on, and I know you are (at least
sometimes) kind of magician ;-)

I was afraid of such thing above because it could be messy even
though it might be useful for reporting one error for one test.

>>     - if it reports "failure" on "you should remove fixed bugs
>>       from list" cases (I mentioned above), since when it
>>       is standalone tests it dictates us to do that.
> Sorry, I did not understand what do you mean here. How is it related to 
> nunit?

In the existing standalone testing, it says like "remove fixed
tests from KnownFailures". What I am afraid is that it might report
the message kinda above as a test failure. Now that it turned out
that it is not integrated to the existing NUnit tests, we don't
have to worry about such things could be reported as a build/test
breakage, but it was what I have worried about.

So, now that it will not (or does not always) affect on the
build process, I think there is nothing to stop you ;-)

Atsushi Eno

More information about the Mono-devel-list mailing list