[Mono-devel-list] Contributing Mainsoft System.Web test suite
Gonzalo Paniagua Javier
gonzalo at ximian.com
Fri Jun 3 07:29:11 EDT 2005
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
> The NUnit (acting as a System.Net client), need to have the following
> * 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
> * 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 }:-).
More information about the Mono-devel-list