On Jan 28, 2008 6:34 PM, Paul LeoNerd Evans <[EMAIL PROTECTED]> wrote: > I'm finding it difficult to come up with a good testing strategy for an > XS module that's just a thin wrapper around an OS call, without > effectively also testing that function itself. Since its behaviour has > minor variations from system to system, writing a test script that can > cope is getting hard. > > The code is the 0.08 developer releases of Socket::GetAddrInfo;
If you *only* test the wrapper and not the OS call at all, then people who see all the tests passing will mistakenly assume that they now have a working way to get socket address info, even though that's still unknown. It would be best to test both, and decouple them so as a developer receiving FAIL reports (or a user running tests) you can tell the difference between the two. -Ken
