yellow.flying wrote:
>> Let me just second this, especially when working with wc-ng. Almost
>> every test hits the working copy, and most exercise it in different
>> ways. We currently have 1145 tests that expected to pass, and some of
>> my initial patches only fail on one or two of them. Running the
>> entire test suite means I get lots of testing on my patch, and I don't
>> have to guess where the 0.2% of tests that fail might be.
>>
> Some times it takes more than one hour or even longer.
There are ways to speed up tests, using RAM disks for repository
storage. It's all in the README.
> And it is strange that
> When I run all tests together some tests fail, but when I run them seperately,
> they will be passed.
>
That is most likely a bug in one of the previous tests that doesn't
properly clean up after itself. Finding these is one of the reasons that
it's a good idea to run all the tests every once in a while.
-- Brane
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2381327
Received on 2009-08-07 16:51:42 CEST