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

RafaelMizrahi rafim at mainsoft.com
Mon Jun 20 10:03:04 EDT 2005

Hi Gonzalo,
Here it is ! System Web Harness integrated with NUnit and tested it on mono.

How can I send you the zip files? Since it is approximately 11MB, ximian
mail server rejects the email.

<Client-side test framework>
SystemWebTestSuite.zip - Web Harness integrated with NUnit 
<Server-side web application>
System_Web_dll.zip - 479 System.Web tests + empty System.Web tests templates
GHTWebControls.zip - web test control container 
GHTWebUtils.zip - web tests base and helper functions

TODO Roadmap:
* Transfer the files to your computer ;)
* Waiting for your review.
* Insert into SVN, and we will proceed the work from there.
I left this task to you, so you can decide where to put each component, and
how to integrate it with build and XSP.
* Mainsoft will abandon its previous harness, and will start using this
harness from the SVN.

May the 'source' be with you.
Mizrahi Rafael
SDE/T Team Leader

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

> 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.


-----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
> 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
> XMLDiff or "in-house" developed XMLDiff component.


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


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

More information about the Mono-devel-list mailing list