[Mono-devel-list] Contributing Mainsoft System.Web test suite

[RafaelMizrahi]

> Should we just use regular NUnit for those?
Well, I guess so.
The web testing framework targets two needs:
* Testing the rendering of web elements.
* Running tests under web context.
* Automate IE and post back. But we currently excluded this feature.

Although, it can be used for testing any class. In fact, we are using this
framework for testing other assemblies which we want to test in web context
(e.g. globalization, reflection). 

I have looked into the 479 tests and about 50 tests are "non rendering"
tests, for example: HttpSessionState, HttpApplicationState, but must be
tested in the context of a web application, so they cannot be used in NUnit.

So, let's agree that classes which can be used outside of ASP.NET (web
context), will be tested using NUnit tests.

rafi

-----Original Message-----
From: Gonzalo Paniagua Javier [mailto:gonzalo at ximian.com] 
Sent: Wednesday, June 15, 2005 7:52 PM
To: RafaelMizrahi
Cc: mono-devel-list at lists.ximian.com; Oved; Vladimir Krasnov
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

On Wed, 2005-06-15 at 17:03 +0300, RafaelMizrahi wrote:
> Hi Gonzalo,
> * We are doing some last cleanups on the web test suite and the tests base
> classes, I hope to send it (along with 479 tests! ;) for your review in
few
> days.
> * The same harness is used for two scenarios:
>     * Generating expected xml files (ASP.NET on IIS). 
>       Scenario is in use only once, every .NET Service Pack.
>     * Getting xml files from web server (Tomcat, xsp, ...) and comparing 
>       with expected xml files.
> * XHTML - We replaced the usage of SGMLReader with htmlagilitypack.
> * XMLDiff - If we wish to replace the XMLDiffPath , we can use
XMLUnit,java
> XMLDiff or "in-house" developed XMLDiff component.

Nice.

What about some classes such as HttpUtility that can be used from
outside of an asp.net application? Should we just use regular nunit for
those?

-Gonzalo