Running tests on windows

Mads Kiilerich mads at kiilerich.com
Thu Mar 22 09:31:51 CDT 2012


On 03/21/2012 11:41 PM, Angel Ezquerra Moreu wrote:
> On Wed, Mar 21, 2012 at 4:25 PM, Mads Kiilerich<mads at kiilerich.com>  wrote:
>> On 03/21/2012 04:09 PM, Angel Ezquerra Moreu wrote:
>>>
>>> I think that hackable mercurial was a very big step forward to make it
>>> easier for us windows users to start to contribute. The fact that the
>>> test suite cannot be run as-is is yet another obstacle that I wish was
>>> not there. Even though thanks to your efforts it is now possible to
>>> run part of the test suite on windows, it is not quite as easy as
>>> running it on Linux yet.
>>
>>
>> Really?
>>
>> The test suite _do_ run as-is when you have MSYS. But granted, it requires a
>> posix environment with sh and other tools, something that "all" unix systems
>> have preinstalled.
>
> That is exactly what I meant, plus the fact that apparently not all
> tests run on windows, even on MSYS.

Some tests do test functionality that is platform specific, so no 
platform is able to run all the tests.

One of the main reasons tests are skipped on windows is that many tests 
exercise posix symlinks or execute bits. The solution to that (in the 
existing sh test framework) will be to make parts of the tests 
conditional instead of having to skip whole tests.

Another thing that is missing is a reliable way to control sub processes 
(such as hgweb) on windows.

The current criteria for skipping tests on windows is also very 
coarse-grained and could probably be tuned a lot.

/Mads


More information about the Mercurial-devel mailing list