I'm writing a translation wrapper (very high surface area:volume), but I might have the advantage that A and B are in my project, so I can have a good idea of how they behave. C isn't, but I have an additional test suite for the small bit I use, just to make sure it behaves reasonably well, and that if it doesn't, that I recognize something is wrong.
Re:How is LLVM tested?
by jjoonathan on Friday March 25, 2016 @07:59PM
(#11363676)
Yeah, that's reasonable -- haven't had to do that yet in production but I'd probably do the same.
As always, exceptions: algorithms, logic hairballs, parsers, anything with a sufficiently low surface-area:volume is likely to generate significant bugs in the interior, so it can likely benefit from a unit test.