Program logic bugs vs input/environmental errors

[Walter Bright via Digitalmars-d]

On 10/16/2014 12:56 PM, Dicebot wrote:
> On Thursday, 16 October 2014 at 19:35:40 UTC, Walter Bright wrote:
>> Ok, but why would 3rd party library unittests be a concern? They shouldn't
>> have shipped it if their own unittests fail - that's the whole point of having
>> unittests.
>
> Libraries tend to be forked and modified.

If you're willing to go that far, then yes, you do wind up owning the unittests, 
in which case s/assert/myassert/ should do it.


> Libraries aren't always tested in
> environment similar to specific production case.

Unittests should not be testing their environment. They should be testing the 
function's logic, and should mock up input for them as required.


> At the same time not being able
> to use same test runner in all Continious Integration jobs greatly reduces the
> value of having standard unittest blocks in the very first place.

I understand that, but wouldn't you be modifying the unittests anyway if using 
an external test runner tool?