Windows Tests

[Martin Geisler]

Peter Arrenbrecht <peter.arrenbrecht at gmail.com> writes:

Hi Anna-Christina,

Thanks for working on this! The lack of proper Windows testing has
bothered me ever since I joined the project... but since I'm a Linux
user it bothered me in a somewhat academic sense :)

> On Thu, May 5, 2011 at 10:06 AM, Friedrich, Anna-Christina
> <Anna-Christina.Friedrich at draeger.com> wrote:
>> I know cmd.exe is not as powerful.
>> Martin pointed out the right thing which is essential for our use of mercurial:
>>
>>>I think part of the fun is to run the commands using cmd.exe -- this
>>>is what most users will end up doing, so if the test suite is to have
>>>any value, we need to test in that environment.
>>
>>
>> As I mentioned before, I implemented a converter tool, which made
>> approximately 130 tests executable on Windows. The tool turns .t
>> files into batch files. It is not perfect and once in a while you
>> have to adjust some parts manually. The major benefit is that those
>> tests run via cmd.exe.
>
> Can these "once in a while" things be addressed with Matt's (U) and
> (W) prefixes so that your conversion would be fully automatic, that
> is, not requiring us to maintain tests as both .t and .bat files?
> -parren

Yes, that sounds like the right way to do it: convert .t files to .bat
files on-the-fly when tests are run on Windows and use the U/W prefixes
as hints to this conversion process.

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://mercurial.aragost.com/kick-start/