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

RafaelMizrahi rafim at mainsoft.com
Sat Jun 4 03:29:51 EDT 2005

Hi Gonzalo,

> Mono.WebServer
Remember that Mainsoft does not use Mono.WebServer, we use Tomcat or other
Application Server, and I prefer that we will choose components that both of
us will use.

> Don't we need a POST too
I rather postpone this to a secondary phase.

> We need to lobby Atsushi
Atsushi can own the XMLDiff/XMLAssert component.

If we want to get things started:
* Our tests already written in VB, is this a problem ?
* You can start creating the NUnit helper classes.
* I will start writing a small "Expected Results Generator" (xml files)
* I will do some cleanups in our web tests helper classes. So we can put
them in SVN.


-----Original Message-----
From: mono-devel-list-bounces at lists.ximian.com
[mailto:mono-devel-list-bounces at lists.ximian.com] On Behalf Of Gonzalo
Paniagua Javier
Sent: Friday, June 03, 2005 2:29 PM
To: mono-devel-list at lists.ximian.com
Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite

On Fri, 2005-06-03 at 12:55 +0300, RafaelMizrahi wrote:
> Hi Gonzalo,
> Using NUnit as the harness and the tests as a web application, is indeed
> of the options. 

Moreover, to avoid the need for running xsp externally, we could just
use Mono.WebServer.

> The NUnit (acting as a System.Net client), need to have the following
> components:
> * GET a web page (use System.NET)

Don't we need a POST too? For example, sometimes we might want to
emulate a button pressed...

> * Extract the elements which participate in the test (we used DIV with ID
> starting with a known prefix (for example TESTxxx)). You don't need the
> whole BODY.
> * XHTML in order to transform the HTML into a well formed XML. (we used
> SGMLReader) 
> * Customized Clean the XML. To remove elements which can fail the test.
> example, ID attributes that are generated by the server, that can be
> different on every GET.
> * XMLDiff the result with an expected result generated previously using
> We used Microsoft XMLDiffPatch. We can evaluate the XMLUnit project,
> create some sort of XMLAssert.

We need to lobby Atsushi and get a tool similar to that one that works
with mono }:-).


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

More information about the Mono-devel-list mailing list