[Mono-devel-list] patch for System.IO

Gert Driesen gert.driesen at pandora.be
Sat Apr 12 16:39:54 EDT 2003

shouldn't we use nunit2 for all (new) testcases ?  that way test classes no
longer have to derive from TestCase and we can convert current test cases to
use the ExpectedException attribute, which can clean up lots of testers ...

is nunit2 also included in the binary distribution of mono ?


----- Original Message ----- 
From: "ville" <vi64pa at kolumbus.fi>
To: "mono-devel" <mono-devel-list at lists.ximian.com>
Sent: Saturday, April 12, 2003 9:31 PM
Subject: Re: [Mono-devel-list] patch for System.IO

On Saturday 12 April 2003 21:15, Gonzalo Paniagua Javier wrote:
> El sáb, 12 de 04 de 2003 a las 18:08, ville escribió:
> > Hi
> >
> > Here is a little patch for System.IO. I have added some test cases to
> > Test/System.IO/StringWriterTest.cs StringReaderTest.cs and
> > FileStreamTest.cs. This patch solves many problems shown by tests, but
> > not all.
> > I'll commit if nobody objects.
> Oh. I've just commited some fixes for other FileStreamTest problems.
> Just check that the test that are currently passing don't get broken and
> that they break in the same place when your patch is applied.

:) Your fixes to FileStream.cs make my fixes to FileStream needless. But
there are still some fixes to StringReader and StringWriter.

> Btw, I think we should split those big tests into smaller ones. At least
> on new tests.

Yeah, that's true.


Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com

More information about the Mono-devel-list mailing list