Windows Tests

[Friedrich, Anna-Christina]

Maybe you can implement the changes I mentioned before (adjust hg.bat and run-tests.py) as a first step. 
That would be very helpful for us.

Furthermore we'd like to participate in implementations that go beyond our "Windows Testing with Batch Files".
It's an interesting approach to add markers to the .t format. But consider for example functions in .t files.
I converted those to labels in Batch, otherwise it won't work on Windows. 
Consider following as well:

$ cat >> $HGRCPATH <<EOF
  > [extensions]
  > convert=
  > [convert]
  > hg.saverev=False
  > EOF

There are also for and if blocks, that have different syntax for Windows.

Therefore you have to change almost everything, except of hg-commands 
-> is it really useful to plaster .t files with markers?

Best regards

Anna Friedrich


-----Original Message-----
From: Peter Arrenbrecht [mailto:peter.arrenbrecht at gmail.com] 
Sent: Montag, 25. April 2011 08:15
To: Matt Mackall
Cc: Greg Ward; mercurial-devel at selenic.com; Friedrich, Anna-Christina; Adrian Buehlmann
Subject: Re: Windows Tests

On Sun, Apr 24, 2011 at 7:29 PM, Matt Mackall <mpm at selenic.com> wrote:
> On Sat, 2011-04-23 at 21:22 -0400, Greg Ward wrote:
>> On 22 April 2011, Matt Mackall said:
>> > To the extent that these sorts of conversions are mechanical, we 
>> > probably want to figure out how to unify them with our existing .t 
>> > files so we don't need to duplicate everything.
>> >
>> > My thought is we can add some new markers to the .t format for 
>> > Windows/Unix-specific commands and responses:
>> >
>> >   $ hg status
>> >   [U] foo/bar
>> >   [W] foo\bar
>> >
>> >   [U] $ cat foo
>> >   [W] $ type foo
>> >   This is the contents of foo.
>>
>> Eek.  I just checked the calendar -- you're almost a month late for 
>> April Fool's Day!
>>
>> Perhaps you chose bad examples: IMHO run-tests.py can and should 
>> paper over simple, obvious, common things like / vs \ and cat vs type.
>
> Actually, no, it probably shouldn't paper over / vs \. That's the sort 
> of thing we want to test for.

How about Adrian's proposal for mode-change commands? Then we would have fairly unobtrusive control of when things are getting papered over.
-parren
---
This communication contains confidential information. If you are not the intended recipient please return this email to the sender and delete it from your records.

Diese Nachricht enthält vertrauliche Informationen. Sollten Sie nicht der beabsichtigte Empfänger dieser E-mail sein, senden Sie bitte diese an den Absender zurück und löschen Sie die E-mail aus Ihrem System.