[Mono-devel-list] OASIS XSLT tests converted to nunit
atsushi at ximian.com
Mon Jul 11 03:46:26 EDT 2005
It's not only for automatic test runners.
--with-test-config will still not be enough since there are several
possibile conbination of flags for manual testing. And if it forces
developers to create such possible configurations every time, or
having several configuration files, it messes developers (at least
I don't want to do that). Beauty should not precede real usability.
> We strive for unity.
> We don't want to have different approaches across frameworks.
> See Ben Maurer response to Environment Variables:
>>It should not mess testers by forcing them edit
>>application config files every time
> As I know developers/testers, their first solution will be to hijack the
> file, so it's just a question of which file will they hijack? The makefile
> or the App.config file. Non of the answers is good.
> -----Original Message-----
> From: Atsushi Eno [mailto:atsushi at ximian.com]
> Sent: Monday, July 11, 2005 5:24 AM
> To: RafaelMizrahi
> Cc: 'Andrew Skiba'; Oved; 'mono-devel mailing list'
> Subject: Re: [Mono-devel-list] OASIS XSLT tests converted to nunit
> 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").
> Atsushi Eno
> RafaelMizrahi wrote:
>>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.
>>From: mono-devel-list-bounces at lists.ximian.com
>>[mailto:mono-devel-list-bounces at lists.ximian.com] On Behalf Of Andrew
>>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
>>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).
>>Mono-devel-list mailing list
>>Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list