Parallel execution of unittests

Andrei Alexandrescu via Digitalmars-d digitalmars-d at puremagic.com
Mon May 5 11:29:46 PDT 2014


On 5/5/14, 11:25 AM, Dicebot wrote:
> On Monday, 5 May 2014 at 18:24:43 UTC, Andrei Alexandrescu wrote:
>> On 5/5/14, 10:08 AM, Dicebot wrote:
>>> On Monday, 5 May 2014 at 16:33:42 UTC, Andrei Alexandrescu wrote:
>>>> On 5/5/14, 8:55 AM, Dicebot wrote:
>>>>>
>>>>> It was just a most simple example. "Unittests should do no I/O because
>>>>> any sort of I/O can fail because of reasons you don't control from the
>>>>> test suite" is an appropriate generalization of my statement.
>>>>>
>>>>> Full /tmp is not a problem, there is nothing broken about system with
>>>>> full /tmp. Problem is test reporting that is unable to connect failure
>>>>> with /tmp being full unless you do environment verification.
>>>>
>>>> Different strokes for different folks. -- Andrei
>>>
>>> There is nothing subjective about it.
>>
>> Of course there is. -- Andrei
>
> You are not helping your point to look reasonable.

My understanding here is you're trying to make dogma out of engineering 
choices that may vary widely across projects and organizations. No thanks.

Andrei



More information about the Digitalmars-d mailing list