Hello, Chris.
Are you sure you compiled the sources from the attached zip? Because in
those sources I see code
Console.WriteLine (res);
Assert.AreEqual (@spana
href=#_SkipLinkimg alt=Skip Navigation Links height=0
width=0
On Sun, 2006-05-07 at 02:19 -0700, Andrew Skiba wrote:
I've fixed bug #78256, so things ought to work with mono now.
Thanks a lot. This fixes the bug I found, but it seems that there is
another one. I attach the whole application sources, in the case you
want to reproduce the problem.
Why not adopt this to be part of the unit tests directly?
That's definitely the idea - the patch just didn't provide
any changes to the existing unit tests.
My colleges Tal and Yoni are going to commit few tests as soon as this
framework is ready.
And if this is not possible, we
Hello,
I like this idea, definitely put it in svn. Maybe under the
Test/mainsoft directory until we start using it for the individual unit
tests?
Why not adopt this to be part of the unit tests directly?
And if this is not possible, we should add it as another check so we can
use make
On Sat, 2006-05-06 at 13:45 -0400, Miguel de Icaza wrote:
Hello,
I like this idea, definitely put it in svn. Maybe under the
Test/mainsoft directory until we start using it for the individual unit
tests?
Why not adopt this to be part of the unit tests directly?
That's definitely the
I like this idea, definitely put it in svn. Maybe under the
Test/mainsoft directory until we start using it for the individual unit
tests?
One thing, though, We shouldn't ever write unit tests that use direct
string comparisons to validate generated html. The only real exception
(that I can
