Hi Gonzalo, Vladimir has finished the prototype of the System.Web test suite engine. The same framework will be used to generate the expected xml (html) results and to verify them.
We have 2 problematic components that I need your help with: ========================= 1. The SGMLReader XHTML component ========================= 1.a. Has a serious bug which is reproducible in Mainsoft and in mono. The bug: Only one attribute from each tag (that has more than one attributes) processed to the output. 1.b The license does not look promising. We need to decide on an alternative component. I should remind that we previously used the COM version "tidy" (which is just a wrapper on-top of tidy library) and it was pretty immature. I will assign Vladimir to check the htmlagilitypack which contains no license. Maybe we should mail the author [EMAIL PROTECTED] ? http://blogs.msdn.com/smourier/archive/2003/06/04/8265.aspx ========================= 2. The XMLDiff component. ========================= The Microsoft XMLDiffPath component seems to work as expected on GH and on mono. If we will have license (or functional) problems we can always replace it (maybe with XMLUnit). Any progress with Atsushi on having our own XMLDiff? Rafi SDE/T Team Leader -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of RafaelMizrahi Sent: Saturday, June 04, 2005 10:30 AM To: [EMAIL PROTECTED]; mono-devel-list@lists.ximian.com Subject: RE: [Mono-devel-list] Contributing Mainsoft System.Web test suite 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. Rafi -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gonzalo Paniagua Javier Sent: Friday, June 03, 2005 2:29 PM To: mono-devel-list@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 one > 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. For > 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 IIS. > We used Microsoft XMLDiffPatch. We can evaluate the XMLUnit project, and/or > create some sort of XMLAssert. We need to lobby Atsushi and get a tool similar to that one that works with mono }:-). -Gonzalo _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
