[Mono-devel-list] OASIS XSLT tests converted to nunit
atsushi at ximian.com
Sun Jul 10 22:24:09 EDT 2005
This time no. It should not mess testers by forcing them edit
application config files every time, rather than just setting
environment variables in their command line (including make
command line options such as "make BLAH=yes run-test").
> You should use ConfigurationSettings.AppSettings with an App.Config file,
> instead of using Environment variables.
> Vladimir already used this approach in the System.Web NUnit Test suite we
> contributed to mono, which also utilizes the NUnit [Suite] attribute.
> Mainsoft SDE/T
> -----Original Message-----
> From: mono-devel-list-bounces at lists.ximian.com
> [mailto:mono-devel-list-bounces at lists.ximian.com] On Behalf Of Andrew Skiba
> Sent: Wednesday, July 06, 2005 2:38 PM
> To: Atsushi Enomoto
> Cc: mono-devel mailing list
> Subject: [Mono-devel-list] OASIS XSLT tests converted to nunit
> Hi Eno.
> I did what we talked about 2 days ago.
> So I converted the standalone testsuite to be an NUnit [Suite]. I did
> not want to support few entry points, so I made dll instead of exe
> (exactly as in W3C xmlconf). To create reference results on dotnet I
> made a separate module, generate.cs. So to avoid code duplication, I
> took the common code from xslttest.cs and generate.cs into
> XsltTestUtils.cs. Another thing one may ask is why did I introduced all
> these env variables. The answer is - I could not parse command line
> anymore, so I made the simpliest change. More elegant way was to make
> few fixtures for every possible combination of whitespace and DOM flags,
> but I'm not sure it's worth the effort right now. Another problem with
> this idea is that generation and the testing would have different flags.
> Some more info can be found in README file (after patching it, of course).
> Thank you.
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list