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; see http://search.cpan.org/~pevans/Socket-GetAddrInfo-0.08_5/ for latest. The code itself seems to be behaving on most platforms; most of the test failures come from such things as different OSes behaving differently if asked to resolve a host called "something.invalid", or quite whether any system knows the "ftp" service, or what happens if it wants to reverse resolve unnamed 1918 addresses (e.g. 192.168.2.2). The smoke testers page is showing a number of FAILs on most platforms not Linux (where I develop), probably because of assumptions the tests make that don't hold there any more. E.g. one problem I had was BSD4.4-based systems, whose struct sockaddr_in includes the sin_len field. http://cpantesters.perl.org/show/Socket-GetAddrInfo.html Does anyone have any strategy suggestions for this? -- Paul "LeoNerd" Evans [EMAIL PROTECTED] ICQ# 4135350 | Registered Linux# 179460 http://www.leonerd.org.uk/
signature.asc
Description: PGP signature
