[Mono-devel-list] Corlib test cases
dave-monolist at earth.li
Sat Jan 24 03:55:29 EST 2004
On Fri, Jan 23, 2004 at 08:14:02PM +0900, Nick Drochak wrote:
> The corlib tests all pass for me on windows (.NET 1.1). So any failures
> when run on mono (Linux or Windows) indicate at the least a compatibility
> issue, and at worst an honest-to-goodness bug.
Do we care what order we check the parameters to a method that has
several parameters and may throw ArgumentException or
ArgumentOutOfRangeException depending on which parameter you get wrong?
If you get several parameters wrong, we could report a different problem
> I started a kind of convention before where I'd enter a bug and then put an
> [Ignore] on that test with a comment with the bug number in it. Then once
> bugs are closed we can re-enable those tests and make sure the bug really
> was fixed. If we could make this re-enable happen automagically, that would
> be great. Any ideas there?
I might well go for continuing along that line, however I cannot think
of a way of automating the re-enabling. I don't really want to make
fixing a bug any harder than it is at the moment. Maybe a script that
just tests the ones that are ignored in such a manner, giving a list of
tests that are ignored but a) still fail, and b) pass. Could NAnt be
augmented in such a way?
To understand recursion, we must first understand recursion.
More information about the Mono-devel-list